Group communication signaling overload mitigation

ABSTRACT

A user plane function (UPF) receives, from a session management function (SMF), a session configuration message. The session configuration message comprises a packet detection rule (PDR) for a group communication session. The PDR comprises a multicast address mapped to a plurality of wireless devices associated with the group communication session. The PDR comprises a forwarding rule for packets associated with the multicast address. Data packets comprising the multicast address are received. Based on the PDR, the data packets are sent to the plurality of wireless devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/843,132, filed May 3, 2019, which is hereby incorporated by referencein its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per anaspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a networknode in a 5G system as per an aspect of an embodiment of the presentdisclosure.

FIG. 4 is a system diagram of an example network node as per an aspectof an embodiment of the present disclosure.

FIG. 5A and FIG. 5B depict two registration management state models inUE 100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 6A and FIG. 6B depict two connection management state models in UE100 and AMF 155 as per an aspect of embodiments of the presentdisclosure.

FIG. 7 is diagram for classification and marking traffic as per anaspect of an embodiment of the present disclosure.

FIG. 8 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 9 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 10 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 11 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 12 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 13 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 14 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 15 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 16 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 17 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 18 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 19 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 20 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 21 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 22 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 23 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 24 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 25 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 26 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 27 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 28 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 30 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 31 is an example call flow as per an aspect of an embodiment of thepresent disclosure.

FIG. 32 is an example diagram as per an aspect of an embodiment of thepresent disclosure.

FIG. 33 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable implementation ofenhanced features and functionalities in 5G systems. Embodiments of thetechnology disclosed herein may be employed in the technical field of 5Gsystems and network slicing for communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to 5G core network and 5G systems for network slicing incommunication systems. Throughout the present disclosure, UE, wirelessdevice, and mobile device are used interchangeably.

The following acronyms are used throughout the present disclosure:

5G 5th generation mobile networks

5GC 5G Core Network

5GS 5G System

5G-AN 5G Access Network

5QI 5G QoS Indicator

AF Application Function

AMF Access and Mobility Management Function

AN Access Network

CDR Charging Data Record

CCNF Common Control Network Functions

CIoT Cellular IoT

CN Core Network

CP Control Plane

DDN Downlink Data Notification

DL Downlink

DN Data Network

DNN Data Network Name

F-TEID Fully Qualified TEID

GPSI Generic Public Subscription Identifier

GTP GPRS Tunneling Protocol

GUTI Globally Unique Temporary Identifier

IMSI International Mobile Subscriber Identity

LADN Local Area Data Network

LI Lawful Intercept

MEI Mobile Equipment Identifier

MICO Mobile Initiated Connection Only

MME Mobility Management Entity

MO Mobile Originated

MSISDN Mobile Subscriber ISDN

MT Mobile Terminating

N3IWF Non-3GPP InterWorking Function

NAI Network Access Identifier

NAS Non-Access Stratum

NB-IoT Narrow Band IoT

NEF Network Exposure Function

NF Network Function

NGAP Next Generation Application Protocol

NR New Radio

NRF Network Repository Function

NSI Network Slice Instance

NSSAI Network Slice Selection Assistance Information

NSSF Network Slice Selection Function

OCS Online Charging System

OFCS Offline Charging System

PCF Policy Control Function

PDU Packet/Protocol Data Unit

PEI Permanent Equipment Identifier

PLMN Public Land Mobile Network

RAN Radio Access Network

QFI QoS Flow Identity

RM Registration Management

S1-AP S1 Application Protocol

SBA Service Based Architecture

SEA Security Anchor Function

SCM Security Context Management

SMF Session Management Function

SMSF SMS Function

S-NSSAI Single Network Slice Selection Assistance information

SUCI Served User Correlation ID

SUPI Subscriber Permanent Identifier

TEID Tunnel Endpoint Identifier

TSN Time Sensitive Networking

UE User Equipment

UL Uplink

UL CL Uplink Classifier

UPF User Plane Function

Example FIG. 1 and FIG. 2 depict a 5G system comprising of accessnetworks and 5G core network. An example 5G access network may comprisean access network connecting to a 5G core network. An access network maycomprise an NG-RAN 105 and/or non-3GPP AN 165. An example 5G corenetwork may connect to one or more 5G access networks 5G-AN and/orNG-RANs. 5G core network may comprise functional elements or networkfunctions as in example FIG. 1 and example FIG. 2 where interfaces maybe employed for communication among the functional elements and/ornetwork elements.

In an example, a network function may be a processing function in anetwork, which may have a functional behavior and/or interfaces. Anetwork function may be implemented either as a network element on adedicated hardware, and/or a network node as depicted in FIG. 3 and FIG.4, or as a software instance running on a dedicated hardware and/orshared hardware, or as a virtualized function instantiated on anappropriate platform.

In an example, access and mobility management function, AMF 155, mayinclude the following functionalities (some of the AMF 155functionalities may be supported in a single instance of an AMF 155):termination of RAN 105 CP interface (N2), termination of NAS (N1), NASciphering and integrity protection, registration management, connectionmanagement, reachability management, mobility management, lawfulintercept (for AMF 155 events and interface to LI system), providetransport for session management, SM messages between UE 100 and SMF160, transparent proxy for routing SM messages, access authentication,access authorization, provide transport for SMS messages between UE 100and SMSF, security anchor function, SEA, interaction with the AUSF 150and the UE 100, receiving the intermediate key established as a resultof the UE 100 authentication process, security context management, SCM,that receives a key from the SEA that it uses to derive access networkspecific keys, and/or the like.

In an example, the AMF 155 may support non-3GPP access networks throughN2 interface with N3IWF 170, NAS signaling with a UE 100 over N3IWF 170,authentication of UEs connected over N3IWF 170, management of mobility,authentication, and separate security context state(s) of a UE 100connected via non-3GPP access 165 or connected via 3GPP access 105 andnon-3GPP access 165 simultaneously, support of a coordinated RM contextvalid over 3GPP access 105 and non 3GPP access 165, support of CMmanagement contexts for the UE 100 for connectivity over non-3GPPaccess, and/or the like.

In an example, an AMF 155 region may comprise one or multiple AMF 155sets. The AMF 155 set may comprise some AMF 155 that serve a given areaand/or network slice(s). In an example, multiple AMF 155 sets may be perAMF 155 region and/or network slice(s). Application identifier may be anidentifier that may be mapped to a specific application trafficdetection rule. Configured NSSAI may be an NSSAI that may be provisionedin a UE 100. DN 115 access identifier (DNAI), for a DNN, may be anidentifier of a user plane access to a DN 115. Initial registration maybe related to a UE 100 registration in RM-DEREGISTERED 500, 520 states.N2AP UE 100 association may be a logical per UE 100 association betweena 5G AN node and an AMF 155. N2AP UE-TNLA-binding may be a bindingbetween a N2AP UE 100 association and a specific transport networklayer, TNL association for a given UE 100.

In an example, session management function, SMF 160, may include one ormore of the following functionalities (one or more of the SMF 160functionalities may be supported in a single instance of a SMF 160):session management (e.g. session establishment, modify and release,including tunnel maintain between UPF 110 and AN 105 node), UE 100 IPaddress allocation & management (including optional authorization),selection and control of UP function(s), configuration of trafficsteering at UPF 110 to route traffic to proper destination, terminationof interfaces towards policy control functions, control part of policyenforcement and QoS. lawful intercept (for SM events and interface to LISystem), termination of SM parts of NAS messages, downlink datanotification, initiation of AN specific SM information, sent via AMF 155over N2 to (R)AN 105, determination of SSC mode of a session, roamingfunctionality, handling local enforcement to apply QoS SLAs (VPLMN),charging data collection and charging interface (VPLMN), lawfulintercept (in VPLMN for SM events and interface to LI System), supportfor interaction with external DN 115 for transport of signaling for PDUsession authorization/authentication by external DN 115, and/or thelike.

In an example, a user plane function, UPF 110, may include one or moreof the following functionalities (some of the UPF 110 functionalitiesmay be supported in a single instance of a UPF 110): anchor point forIntra-/Inter-RAT mobility (when applicable), external PDU session pointof interconnect to DN 115, packet routing & forwarding, packetinspection and user plane part of policy rule enforcement, lawfulintercept (UP collection), traffic usage reporting, uplink classifier tosupport routing traffic flows to a data network, branching point tosupport multi-homed PDU session(s), QoS handling for user plane, uplinktraffic verification (SDF to QoS flow mapping), transport level packetmarking in the uplink and downlink, downlink packet buffering, downlinkdata notification triggering, and/or the like.

In an example, the UE 100 IP address management may include allocationand release of the UE 100 IP address and/or renewal of the allocated IPaddress. The UE 100 may set a requested PDU type during a PDU sessionestablishment procedure based on its IP stack capabilities and/orconfiguration. In an example, the SMF 160 may select PDU type of a PDUsession. In an example, if the SMF 160 receives a request with PDU typeset to IP, the SMF 160 may select PDU type IPv4 or IPv6 based on DNNconfiguration and/or operator policies. In an example, the SMF 160 mayprovide a cause value to the UE 100 to indicate whether the other IPversion is supported on the DNN. In an example, if the SMF 160 receivesa request for PDU type IPv4 or IPv6 and the requested IP version issupported by the DNN the SMF 160 may select the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 may support thefollowing mechanisms: during a PDU session establishment procedure, theSMF 160 may send the IP address to the UE 100 via SM NAS signaling. TheIPv4 address allocation and/or IPv4 parameter configuration via DHCPv4may be employed once PDU session may be established. IPv6 prefixallocation may be supported via IPv6 stateless autoconfiguration, ifIPv6 is supported. In an example, 5GC network elements may support IPv6parameter configuration via stateless DHCPv6.

The 5GC may support the allocation of a static IPv4 address and/or astatic IPv6 prefix based on subscription information in a UDM 140 and/orbased on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF 110) may handle the user plane path of PDUsessions. A UPF 110 that provides the interface to a data network maysupport functionality of a PDU session anchor.

In an example, a policy control function, PCF 135, may support unifiedpolicy framework to govern network behavior, provide policy rules tocontrol plane function(s) to enforce policy rules, implement a front endto access subscription information relevant for policy decisions in auser data repository (UDR), and/or the like.

A network exposure function, NEF 125, may provide means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, receiveinformation from other network functions, and/or the like.

In an example, an network repository function, NRF 130 may supportservice discovery function that may receive NF discovery request from NFinstance, provide information about the discovered NF instances (bediscovered) to the NF instance, and maintain information about availableNF instances and their supported services, and/or the like.

In an example, an NSSF 120 may select a set of network slice instancesserving the UE 100, may determine allowed NSSAI. In an example, the NSSF120 may determine the AMF 155 set to be employed to serve the UE 100,and/or, based on configuration, determine a list of candidate AMF 155(s)155 by querying the NRF 130.

In an example, stored data in a UDR may include at least usersubscription data, including at least subscription identifiers, securitycredentials, access and mobility related subscription data, sessionrelated subscription data, policy data, and/or the like.

In an example, an AUSF 150 may support authentication server function(AUSF 150).

In an example, an application function, AF 145, may interact with the3GPP core network to provide services. In an example, based on operatordeployment, application functions may be trusted by the operator tointeract directly with relevant network functions. Application functionsnot allowed by the operator to access directly the network functions mayuse an external exposure framework (e.g., via the NEF 125) to interactwith relevant network functions.

In an example, control plane interface between the (R)AN 105 and the 5Gcore may support connection of multiple different kinds of AN(s) (e.g.3GPP RAN 105, N3IWF 170 for Un-trusted access 165) to the 5GC via acontrol plane protocol. In an example, an N2 AP protocol may be employedfor both the 3GPP access 105 and non-3GPP access 165. In an example,control plane interface between the (R)AN 105 and the 5G core maysupport decoupling between AMF 155 and other functions such as SMF 160that may need to control the services supported by AN(s) (e.g. controlof the UP resources in the AN 105 for a PDU session).

In an example, the 5GC may provide policy information from the PCF 135to the UE 100. In an example, the policy information may comprise:access network discovery and selection policy, UE 100 route selectionpolicy (URSP), SSC mode selection policy (SSCMSP), network sliceselection policy (NSSP), DNN selection policy, non-seamless offloadpolicy, and/or the like.

In an example, as depicted in example FIG. 5A and FIG. 5B, theregistration management, RM may be employed to register or de-register aUE/user 100 with the network, and establish the user context in thenetwork. Connection management may be employed to establish and releasethe signaling connection between the UE 100 and the AMF 155.

In an example, a UE 100 may register with the network to receiveservices that require registration. In an example, the UE 100 may updateits registration with the network periodically in order to remainreachable (periodic registration update), or upon mobility (e.g.,mobility registration update), or to update its capabilities or tore-negotiate protocol parameters.

In an example, an initial registration procedure as depicted in exampleFIG. 8 and FIG. 9 may involve execution of network access controlfunctions (e.g. user authentication and access authorization based onsubscription profiles in UDM 140). Example FIG. 9 is a continuation ofthe initial registration procedure depicted in FIG. 8. As a result ofthe initial registration procedure, the identity of the serving AMF 155may be registered in a UDM 140.

In an example, the registration management, RM procedures may beapplicable over both 3GPP access 105 and non 3GPP access 165.

An example FIG. 5A may depict the RM states of a UE 100 as observed bythe UE 100 and AMF 155. In an example embodiment, two RM states may beemployed in the UE 100 and the AMF 155 that may reflect the registrationstatus of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, andRM-REGISTERED 510. In an example, in the RM DEREGISTERED state 500, theUE 100 may not be registered with the network. The UE 100 context in theAMF 155 may not hold valid location or routing information for the UE100 so the UE 100 may not be reachable by the AMF 155. In an example,the UE 100 context may be stored in the UE 100 and the AMF 155. In anexample, in the RM REGISTERED state 510, the UE 100 may be registeredwith the network. In the RM-REGISTERED 510 state, the UE 100 may receiveservices that may require registration with the network.

In an example embodiment, two RM states may be employed in AMF 155 forthe UE 100 that may reflect the registration status of the UE 100 in theselected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As depicted in example FIG. 6A and FIG. 6B, connection management, CM,may comprise establishing and releasing a signaling connection between aUE 100 and an AMF 155 over N1 interface. The signaling connection may beemployed to enable NAS signaling exchange between the UE 100 and thecore network. The signaling connection between the UE 100 and the AMF155 may comprise both the AN signaling connection between the UE 100 andthe (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2connection for the UE 100 between the AN and the AMF 155.

As depicted in example FIG. 6A and FIG. 6B, two CM states may beemployed for the NAS signaling connectivity of the UE 100 with the AMF155, CM-IDLE 600, 620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600state may be in RM-REGISTERED 510 state and may have no NAS signalingconnection established with the AMF 155 over N1. The UE 100 may performcell selection, cell reselection, PLMN selection, and/or the like. A UE100 in CM-CONNECTED 610 state may have a NAS signaling connection withthe AMF 155 over N1.

In an example embodiment two CM states may be employed for the UE 100 atthe AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

In an example, an RRC inactive state may apply to NG-RAN (e.g. it mayapply to NR and E-UTRA connected to 5G CN). The AMF 155, based onnetwork configuration, may provide assistance information to the NG RAN105, to assist the NG RAN's 105 decision whether the UE 100 may be sentto RRC inactive state. When a UE 100 is CM-CONNECTED 610 with RRCinactive state, the UE 100 may resume the RRC connection due to uplinkdata pending, mobile initiated signaling procedure, as a response to RAN105 paging, to notify the network that it has left the RAN 105notification area, and/or the like.

In an example, a NAS signaling connection management may includeestablishing and releasing a NAS signaling connection. A NAS signalingconnection establishment function may be provided by the UE 100 and theAMF 155 to establish the NAS signaling connection for the UE 100 inCM-IDLE 600 state. The procedure of releasing the NAS signalingconnection may be initiated by the 5G (R)AN 105 node or the AMF 155.

In an example, reachability management of a UE 100 may detect whetherthe UE 100 is reachable and may provide the UE 100 location (e.g. accessnode) to the network to reach the UE 100. Reachability management may bedone by paging the UE 100 and the UE 100 location tracking. The UE 100location tracking may include both UE 100 registration area tracking andUE 100 reachability tracking. The UE 100 and the AMF 155 may negotiateUE 100 reachability characteristics in CM-IDLE 600, 620 state duringregistration and registration update procedures.

In an example, two UE 100 reachability categories may be negotiatedbetween a UE 100 and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100reachability allowing mobile device terminated data while the UE 100 isCM-IDLE 600 mode. 2) Mobile initiated connection only (MICO) mode. The5GC may support a PDU connectivity service that provides exchange ofPDUs between the UE 100 and a data network identified by a DNN. The PDUconnectivity service may be supported via PDU sessions that areestablished upon request from the UE 100.

In an example, a PDU session may support one or more PDU session types.PDU sessions may be established (e.g. upon UE 100 request), modified(e.g. upon UE 100 and 5GC request) and/or released (e.g. upon UE 100 and5GC request) using NAS SM signaling exchanged over N1 between the UE 100and the SMF 160. Upon request from an application server, the 5GC may beable to trigger a specific application in the UE 100. When receiving thetrigger, the UE 100 may send it to the identified application in the UE100. The identified application in the UE 100 may establish a PDUsession to a specific DNN.

In an example, the 5G QoS model may support a QoS flow based frameworkas depicted in example FIG. 7. The 5G QoS model may support both QoSflows that require a guaranteed flow bit rate and QoS flows that may notrequire a guaranteed flow bit rate. In an example, the 5G QoS model maysupport reflective QoS. The QoS model may comprise flow mapping orpacket marking at the UPF 110 (CN_UP) 110, AN 105 and/or the UE 100. Inan example, packets may arrive from and/or destined to theapplication/service layer 730 of UE 100, UPF 110 (CN_UP) 110, and/or theAF 145.

In an example, the QoS flow may be a granularity of QoS differentiationin a PDU session. A QoS flow ID, QFI, may be employed to identify theQoS flow in the 5G system. In an example, user plane traffic with thesame QFI within a PDU session may receive the same traffic forwardingtreatment. The QFI may be carried in an encapsulation header on N3and/or N9 (e.g. without any changes to the end-to-end packet header). Inan example, the QFI may be applied to PDUs with different types ofpayload. The QFI may be unique within a PDU session.

In an example, the QoS parameters of a QoS flow may be provided to the(R)AN 105 as a QoS profile over N2 at PDU session establishment, QoSflow establishment, or when NG-RAN is used at every time the user planeis activated. In an example, a default QoS rule may be required forevery PDU session. The SMF 160 may allocate the QFI for a QoS flow andmay derive QoS parameters from the information provided by the PCF 135.In an example, the SMF 160 may provide the QFI together with the QoSprofile containing the QoS parameters of a QoS flow to the (R)AN 105.

In an example, 5G QoS flow may be a granularity for QoS forwardingtreatment in the 5G system. Traffic mapped to the same 5G QoS flow mayreceive the same forwarding treatment (e.g. scheduling policy, queuemanagement policy, rate shaping policy, RLC configuration, and/or thelike). In an example, providing different QoS forwarding treatment mayrequire separate 5G QoS flows.

In an example, a 5G QoS indicator may be a scalar that may be employedas a reference to a specific QoS forwarding behavior (e.g. packet lossrate, packet delay budget) to be provided to a 5G QoS flow. In anexample, the 5G QoS indicator may be implemented in the access networkby the 5QI referencing node specific parameters that may control the QoSforwarding treatment (e.g. scheduling weights, admission thresholds,queue management thresholds, link layer protocol configuration, and/orthe like.).

In an example, 5GC may support edge computing and may enable operator(s)and 3rd party services to be hosted close to the UE's access point ofattachment. The 5G core network may select a UPF 110 close to the UE 100and may execute the traffic steering from the UPF 110 to the local datanetwork via a N6 interface. In an example, the selection and trafficsteering may be based on the UE's 100 subscription data, UE 100location, the information from application function AF 145, policy,other related traffic rules, and/or the like. In an example, the 5G corenetwork may expose network information and capabilities to an edgecomputing application function. The functionality support for edgecomputing may include local routing where the 5G core network may selecta UPF 110 to route the user traffic to the local data network, trafficsteering where the 5G core network may select the traffic to be routedto the applications in the local data network, session and servicecontinuity to enable UE 100 and application mobility, user planeselection and reselection, e.g. based on input from applicationfunction, network capability exposure where 5G core network andapplication function may provide information to each other via NEF 125,QoS and charging where PCF 135 may provide rules for QoS control andcharging for the traffic routed to the local data network, support oflocal area data network where 5G core network may provide support toconnect to the LADN in a certain area where the applications aredeployed, and/or the like.

An example 5G system may be a 3GPP system comprising of 5G accessnetwork 105, 5G core network and a UE 100, and/or the like. AllowedNSSAI may be an NSSAI provided by a serving PLMN during e.g. aregistration procedure, indicating the NSSAI allowed by the network forthe UE 100 in the serving PLMN for the current registration area.

In an example, a PDU connectivity service may provide exchange of PDUsbetween a UE 100 and a data network. A PDU session may be an associationbetween the UE 100 and the data network, DN 115, that may provide thePDU connectivity service. The type of association may be IP, Ethernetand/or unstructured.

Establishment of user plane connectivity to a data network via networkslice instance(s) may comprise the following: performing a RM procedureto select an AMF 155 that supports the required network slices, andestablishing one or more PDU session(s) to the required data network viathe network slice instance(s).

In an example, the set of network slices for a UE 100 may be changed atany time while the UE 100 may be registered with the network, and may beinitiated by the network, or the UE 100.

In an example, a periodic registration update may be UE 100re-registration at expiry of a periodic registration timer. A requestedNSSAI may be a NSSAI that the UE 100 may provide to the network.

In an example, a service based interface may represent how a set ofservices may be provided/exposed by a given NF.

In an example, a service continuity may be an uninterrupted userexperience of a service, including the cases where the IP address and/oranchoring point may change. In an example, a session continuity mayrefer to continuity of a PDU session. For PDU session of IP type sessioncontinuity may imply that the IP address is preserved for the lifetimeof the PDU session. An uplink classifier may be a UPF 110 functionalitythat aims at diverting uplink traffic, based on filter rules provided bythe SMF 160, towards data network, DN 115.

In an example, the 5G system architecture may support data connectivityand services enabling deployments to use techniques such as e.g. networkfunction virtualization and/or software defined networking. The 5Gsystem architecture may leverage service-based interactions betweencontrol plane (CP) network functions where identified. In 5G systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A 5G system may enable anetwork function to interact with other NF(s) directly if required.

In an example, the 5G system may reduce dependencies between the accessnetwork (AN) and the core network (CN). The architecture may comprise aconverged access-agnostic core network with a common AN-CN interfacewhich may integrate different 3GPP and non-3GPP access types.

In an example, the 5G system may support a unified authenticationframework, stateless NFs, where the compute resource is decoupled fromthe storage resource, capability exposure, and concurrent access tolocal and centralized services. To support low latency services andaccess to local data networks, UP functions may be deployed close to theaccess network.

In an example, the 5G system may support roaming with home routedtraffic and/or local breakout traffic in the visited PLMN. An example 5Garchitecture may be service-based and the interaction between networkfunctions may be represented in two ways. (1) As service-basedrepresentation (depicted in example FIG. 1), where network functionswithin the control plane, may enable other authorized network functionsto access their services. This representation may also includepoint-to-point reference points where necessary. (2) Reference pointrepresentation, showing the interaction between the NF services in thenetwork functions described by point-to-point reference point (e.g. N11)between any two network functions.

In an example, a network slice may comprise the core network controlplane and user plane network functions, the 5G Radio Access Network; theN3IWF functions to the non-3GPP Access Network, and/or the like. Networkslices may differ for supported features and network functionimplementation. The operator may deploy multiple network slice instancesdelivering the same features but for different groups of UEs, e.g. asthey deliver a different committed service and/or because they may bededicated to a customer. The NSSF 120 may store the mapping informationbetween slice instance ID and NF ID (or NF address).

In an example, a UE 100 may simultaneously be served by one or morenetwork slice instances via a 5G-AN. In an example, the UE 100 may beserved by k network slices (e.g. k=8, 16, etc.) at a time. An AMF 155instance serving the UE 100 logically may belong to a network sliceinstance serving the UE 100.

In an example, a PDU session may belong to one specific network sliceinstance per PLMN. In an example, different network slice instances maynot share a PDU session. Different slices may have slice-specific PDUsessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) mayidentify a network slice. An S-NSSAI may comprise a slice/service type(SST), which may refer to the expected network slice behavior in termsof features and services; and/or a slice differentiator (SD). A slicedifferentiator may be optional information that may complement theslice/service type(s) to allow further differentiation for selecting anetwork slice instance from potentially multiple network slice instancesthat comply with the indicated slice/service type. In an example, thesame network slice instance may be selected employing differentS-NSSAIs. The CN part of a network slice instance(s) serving a UE 100may be selected by CN.

In an example, subscription data may include the S-NSSAI(s) of thenetwork slices that the UE 100 subscribes to. One or more S-NSSAIs maybe marked as default S-NSSAI. In an example, k S-NSSAI may be markeddefault S-NSSAI (e.g. k=8, 16, etc.). In an example, the UE 100 maysubscribe to more than 8 S-NSSAIs.

In an example, a UE 100 may be configured by the HPLMN with a configuredNSSAI per PLMN. Upon successful completion of a UE's registrationprocedure, the UE 100 may obtain from the AMF 155 an Allowed NSSAI forthis PLMN, which may include one or more S-NSSAIs.

In an example, the Allowed NSSAI may take precedence over the configuredNSSAI for a PLMN. The UE 100 may use the S-NSSAIs in the allowed NSSAIcorresponding to a network slice for the subsequent network sliceselection related procedures in the serving PLMN.

In an example, the establishment of user plane connectivity to a datanetwork via a network slice instance(s) may comprise: performing a RMprocedure to select an AMF 155 that may support the required networkslices, establishing one or more PDU sessions to the required datanetwork via the network slice instance(s), and/or the like.

In an example, when a UE 100 registers with a PLMN, if the UE 100 forthe PLMN has a configured NSSAI or an allowed NSSAI, the UE 100 mayprovide to the network in RRC and NAS layer a requested NSSAI comprisingthe S-NSSAI(s) corresponding to the slice(s) to which the UE 100attempts to register, a temporary user ID if one was assigned to the UE,and/or the like. The requested NSSAI may be configured-NSSAI,allowed-NSSAI, and/or the like.

In an example, when a UE 100 registers with a PLMN, if for the PLMN theUE 100 has no configured NSSAI or allowed NSSAI, the RAN 105 may routeNAS signaling from/to the UE 100 to/from a default AMF 155.

In an example, the network, based on local policies, subscriptionchanges and/or UE 100 mobility, may change the set of permitted networkslice(s) to which the UE 100 is registered. In an example, the networkmay perform the change during a registration procedure or trigger anotification towards the UE 100 of the change of the supported networkslices using an RM procedure (which may trigger a registrationprocedure). The network may provide the UE 100 with a new allowed NSSAIand tracking area list.

In an example, during a registration procedure in a PLMN, in case thenetwork decides that the UE 100 may be served by a different AMF 155based on network slice(s) aspects, the AMF 155 that first received theregistration request may redirect the registration request to anotherAMF 155 via the RAN 105 or via direct signaling between the initial AMF155 and the target AMF 155.

In an example, the network operator may provision the UE 100 withnetwork slice selection policy (NSSP). The NSSP may comprise one or moreNSSP rules.

In an example, if a UE 100 has one or more PDU sessions establishedcorresponding to a specific S-NSSAI, the UE 100 may route the user dataof the application in one of the PDU sessions, unless other conditionsin the UE 100 may prohibit the use of the PDU sessions. If theapplication provides a DNN, then the UE 100 may consider the DNN todetermine which PDU session to use. In an example, if the UE 100 doesnot have a PDU session established with the specific S-NSSAI, the UE 100may request a new PDU session corresponding to the S-NSSAI and with theDNN that may be provided by the application. In an example, in order forthe RAN 105 to select a proper resource for supporting network slicingin the RAN 105, the RAN 105 may be aware of the network slices used bythe UE 100.

In an example, an AMF 155 may select an SMF 160 in a network sliceinstance based on S-NSSAI, DNN and/or other information e.g. UE 100subscription and local operator policies, and/or the like, when the UE100 triggers the establishment of a PDU session. The selected SMF 160may establish the PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of sliceinformation for the slices the UE 100 may access, when the UE 100 isaware or configured that privacy considerations may apply to NSSAI, theUE 100 may not include NSSAI in NAS signaling unless the UE 100 has aNAS security context and the UE 100 may not include NSSAI in unprotectedRRC signaling.

In an example, for roaming scenarios, the network slice specific networkfunctions in VPLMN and HPLMN may be selected based on the S-NSSAIprovided by the UE 100 during PDU connection establishment. If astandardized S-NSSAI is used, selection of slice specific NF instancesmay be done by one or more PLMN(s) based on the provided S-NSSAI. In anexample, the VPLMN may map the S-NSSAI of HPLMN to a S-NSSAI of VPLMNbased on roaming agreement (e.g., including mapping to a default S-NSSAIof VPLMN). In an example, the selection of slice specific NF instance inVPLMN may be done based on the S-NSSAI of VPLMN. In an example, theselection of any slice specific NF instance in HPLMN may be based on theS-NSSAI of HPLMN.

As depicted in example FIG. 8 and FIG. 9, a registration procedure maybe performed by the UE 100 to get authorized to receive services, toenable mobility tracking, to enable reachability, and/or the like.

In an example, the UE 100 may send to the (R)AN 105 an AN message 805(comprising AN parameters, RM-NAS registration request (registrationtype, SUCI or SUPI or 5G-GUTI, last visited TAI (if available), securityparameters, requested NSSAI, mapping of requested NSSAI, UE 100 5GCcapability, PDU session status, PDU session(s) to be re-activated,Follow on request, MICO mode preference, and/or the like), and/or thelike). In an example, in case of NG-RAN, the AN parameters may includee.g. SUCI or SUPI or the 5G-GUTI, the Selected PLMN ID and requestedNSSAI, and/or the like. In an example, the AN parameters may compriseestablishment cause. The establishment cause may provide the reason forrequesting the establishment of an RRC connection. In an example, theregistration type may indicate if the UE 100 wants to perform an initialregistration (i.e. the UE 100 is in RM-DEREGISTERED state), a mobilityregistration update (e.g., the UE 100 is in RM-REGISTERED state andinitiates a registration procedure due to mobility), a periodicregistration update (e.g., the UE 100 is in RM-REGISTERED state and mayinitiate a registration procedure due to the periodic registrationupdate timer expiry) or an emergency registration (e.g., the UE 100 isin limited service state). In an example, if the UE 100 performing aninitial registration (i.e., the UE 100 is in RM-DEREGISTERED state) to aPLMN for which the UE 100 does not already have a 5G-GUTI, the UE 100may include its SUCI or SUPI in the registration request. The SUCI maybe included if the home network has provisioned the public key toprotect SUPI in the UE. If the UE 100 received a UE 100 configurationupdate command indicating that the UE 100 needs to re-register and the5G-GUTI is invalid, the UE 100 may perform an initial registration andmay include the SUPI in the registration request message. For anemergency registration, the SUPI may be included if the UE 100 does nothave a valid 5G-GUTI available; the PEI may be included when the UE 100has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI may beincluded and it may indicate the last serving AMF 155. If the UE 100 isalready registered via a non-3GPP access in a PLMN different from thenew PLMN (e.g., not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the 3GPP access, the UE 100 may not provide over the3GPP access the 5G-GUTI allocated by the AMF 155 during the registrationprocedure over the non-3GPP access. If the UE 100 is already registeredvia a 3GPP access in a PLMN (e.g., the registered PLMN), different fromthe new PLMN (i.e. not the registered PLMN or an equivalent PLMN of theregistered PLMN) of the non-3GPP access, the UE 100 may not provide overthe non-3GPP access the 5G-GUTI allocated by the AMF 155 during theregistration procedure over the 3GPP access. The UE 100 may provide theUE's usage setting based on its configuration. In case of initialregistration or mobility registration update, the UE 100 may include themapping of requested NSSAI, which may be the mapping of one or moreS-NSSAI of the requested NSSAI to the S-NSSAIs of the configured NSSAIfor the HPLMN, to ensure that the network is able to verify whether theS-NSSAI(s) in the requested NSSAI are permitted based on the subscribedS-NSSAIs. If available, the last visited TAI may be included in order tohelp the AMF 155 produce registration area for the UE. In an example,the security parameters may be used for authentication and integrityprotection. requested NSSAI may indicate the network slice selectionassistance information. The PDU session status may indicates thepreviously established PDU sessions in the UE. When the UE 100 isconnected to the two AMF 155 belonging to different PLMN via 3GPP accessand non-3GPP access then the PDU session status may indicate theestablished PDU session of the current PLMN in the UE. The PDUsession(s) to be re-activated may be included to indicate the PDUsession(s) for which the UE 100 may intend to activate UP connections. APDU session corresponding to a LADN may not be included in the PDUsession(s) to be re-activated when the UE 100 is outside the area ofavailability of the LADN. The follow on request may be included when theUE 100 may have pending uplink signaling and the UE 100 may not includePDU session(s) to be re-activated, or the registration type may indicatethe UE 100 may want to perform an emergency registration.

In an example, if a SUPI is included or the 5G-GUTI does not indicate avalid AMF 155, the (R)AN 105, based on (R)AT and requested NSSAI, ifavailable, may selects 808 an AMF 155. If UE 100 is in CM-CONNECTEDstate, the (R)AN 105 may forward the registration request message to theAMF 155 based on the N2 connection of the UE. If the (R)AN 105 may notselect an appropriate AMF 155, it may forward the registration requestto an AMF 155 which has been configured, in (R)AN 105, to perform AMF155 selection 808.

In an example, the (R)AN 105 may send to the new AMF 155 an N2 message810 (comprising: N2 parameters, RM-NAS registration request(registration type, SUPI or 5G-GUTI, last visited TAI (if available),security parameters, requested NSSAI, mapping of requested NSSAI, UE 1005GC capability, PDU session status, PDU session(s) to be re-activated,follow on request, and MICO mode preference), and/or the like). In anexample, when NG-RAN is used, the N2 parameters may comprise theselected PLMN ID, location information, cell identity and the RAT typerelated to the cell in which the UE 100 is camping. In an example, whenNG-RAN is used, the N2 parameters may include the establishment cause.

In an example, the new AMF 155 may send to the old AMF 155 anNamf_Communication_UEContextTransfer (complete registration request)815. In an example, if the UE's 5G-GUTI was included in the registrationrequest and the serving AMF 155 has changed since last registrationprocedure, the new AMF 155 may invoke theNamf_Communication_UEContextTransfer service operation 815 on the oldAMF 155 including the complete registration request IE, which may beintegrity protected, to request the UE's SUPI and MM Context. The oldAMF 155 may use the integrity protected complete registration request IEto verify if the context transfer service operation invocationcorresponds to the UE 100 requested. In an example, the old AMF 155 maytransfer the event subscriptions information by one or more NF consumer,for the UE, to the new AMF 155. In an example, if the UE 100 identifiesitself with PEI, the SUPI request may be skipped.

In an example, the old AMF 155 may send to new AMF 155 a response 815 toNamf_Communication_UEContextTransfer (SUPI, MM context, SMF 160information, PCF ID). In an example, the old AMF 155 may respond to thenew AMF 155 for the Namf_Communication_UEContextTransfer invocation byincluding the UE's SUPI and MM context. In an example, if old AMF 155holds information about established PDU sessions, the old AMF 155 mayinclude SMF 160 information including S-NSSAI(s), SMF 160 identities andPDU session ID. In an example, if old AMF 155 holds information aboutactive NGAP UE-TNLA bindings to N3IWF, the old AMF 155 may includeinformation about the NGAP UE-TNLA bindings.

In an example, if the SUPI is not provided by the UE 100 nor retrievedfrom the old AMF 155 the identity request procedure 820 may be initiatedby the AMF 155 sending an identity request message to the UE 100requesting the SUCI.

In an example, the UE 100 may respond with an identity response message820 including the SUCI. The UE 100 may derive the SUCI by using theprovisioned public key of the HPLMN.

In an example, the AMF 155 may decide to initiate UE 100 authentication825 by invoking an AUSF 150. The AMF 155 may select an AUSF 150 based onSUPI or SUCI. In an example, if the AMF 155 is configured to supportemergency registration for unauthenticated SUPIs and the UE 100indicated registration type emergency registration the AMF 155 may skipthe authentication and security setup or the AMF 155 may accept that theauthentication may fail and may continue the registration procedure.

In an example, the authentication 830 may be performed byNudm_UEAuthenticate_Get operation. The AUSF 150 may discover a UDM 140.In case the AMF 155 provided a SUCI to AUSF 150, the AUSF 150 may returnthe SUPI to AMF 155 after the authentication is successful. In anexample, if network slicing is used, the AMF 155 may decide if theregistration request needs to be rerouted where the initial AMF 155refers to the AMF 155. In an example, the AMF 155 may initiate NASsecurity functions. In an example, upon completion of NAS securityfunction setup, the AMF 155 may initiate NGAP procedure to enable 5G-ANuse it for securing procedures with the UE. In an example, the 5G-AN maystore the security context and may acknowledge to the AMF 155. The 5G-ANmay use the security context to protect the messages exchanged with theUE.

In an example, new AMF 155 may send to the old AMF 155Namf_Communication_RegistrationCompleteNotify 835. If the AMF 155 haschanged, the new AMF 155 may notify the old AMF 155 that theregistration of the UE 100 in the new AMF 155 may be completed byinvoking the Namf_Communication_RegistrationCompleteNotify serviceoperation. If the authentication/security procedure fails, then theregistration may be rejected, and the new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operation with areject indication reason code towards the old AMF 155. The old AMF 155may continue as if the UE 100 context transfer service operation wasnever received. If one or more of the S-NSSAIs used in the oldregistration area may not be served in the target registration area, thenew AMF 155 may determine which PDU session may not be supported in thenew registration area. The new AMF 155 may invoke theNamf_Communication_RegistrationCompleteNotify service operationincluding the rejected PDU session ID and a reject cause (e.g. theS-NSSAI becomes no longer available) towards the old AMF 155. The newAMF 155 may modify the PDU session status correspondingly. The old AMF155 may inform the corresponding SMF 160(s) to locally release the UE'sSM context by invoking the Nsmf_PDUSession_ReleaseSMContext serviceoperation.

In an example, the new AMF 155 may send to the UE 100 an identityrequest/response 840 (e.g., PEI). If the PEI was not provided by the UE100 nor retrieved from the old AMF 155, the identity request proceduremay be initiated by AMF 155 sending an identity request message to theUE 100 to retrieve the PEI. The PEI may be transferred encrypted unlessthe UE 100 performs emergency registration and may not be authenticated.For an emergency registration, the UE 100 may have included the PEI inthe registration request.

In an example, the new AMF 155 may initiate ME identity check 845 byinvoking the N5g-eir_EquipmentIdentityCheck_Get service operation 845.

In an example, the new AMF 155, based on the SUPI, may select 905 a UDM140. The UDM 140 may select a UDR instance. In an example, the AMF 155may select a UDM 140.

In an example, if the AMF 155 has changed since the last registrationprocedure, or if the UE 100 provides a SUPI which may not refer to avalid context in the AMF 155, or if the UE 100 registers to the same AMF155 it has already registered to a non-3GPP access (e.g., the UE 100 isregistered over a non-3GPP access and may initiate the registrationprocedure to add a 3GPP access), the new AMF 155 may register with theUDM 140 using Nudm_UECM_Registration 910 and may subscribe to benotified when the UDM 140 may deregister the AMF 155. The UDM 140 maystore the AMF 155 identity associated to the access type and may notremove the AMF 155 identity associated to the other access type. The UDM140 may store information provided at registration in UDR, byNudr_UDM_Update. In an example, the AMF 155 may retrieve the access andmobility subscription data and SMF 160 selection subscription data usingNudm_SDM_Get 915. The UDM 140 may retrieve this information from UDR byNudr_UDM_Query(access and mobility subscription data). After asuccessful response is received, the AMF 155 may subscribe to benotified using Nudm_SDM_Subscribe 920 when the data requested may bemodified. The UDM 140 may subscribe to UDR by Nudr_UDM_Subscribe. TheGPSI may be provided to the AMF 155 in the subscription data from theUDM 140 if the GPSI is available in the UE 100 subscription data. In anexample, the new AMF 155 may provide the access type it serves for theUE 100 to the UDM 140 and the access type may be set to 3GPP access. TheUDM 140 may store the associated access type together with the servingAMF 155 in UDR by Nudr_UDM_Update. The new AMF 155 may create an MMcontext for the UE 100 after getting the mobility subscription data fromthe UDM 140. In an example, when the UDM 140 stores the associatedaccess type together with the serving AMF 155, the UDM 140 may initiatea Nudm_UECM_DeregistrationNotification 921 to the old AMF 155corresponding to 3GPP access. The old AMF 155 may remove the MM contextof the UE. If the serving NF removal reason indicated by the UDM 140 isinitial registration, then the old AMF 155 may invoke theNamf_EventExposure_Notify service operation towards all the associatedSMF 160 s of the UE 100 to notify that the UE 100 is deregistered fromold AMF 155. The SMF 160 may release the PDU session(s) on getting thisnotification. In an example, the old AMF 155 may unsubscribe with theUDM 140 for subscription data using Nudm_SDM_unsubscribe 922.

In an example, if the AMF 155 decides to initiate PCF 135 communication,e.g. the AMF 155 has not yet obtained access and mobility policy for theUE 100 or if the access and mobility policy in the AMF 155 are no longervalid, the AMF 155 may select 925 a PCF 135. If the new AMF 155 receivesa PCF ID from the old AMF 155 and successfully contacts the PCF 135identified by the PCF ID, the AMF 155 may select the (V-)PCF identifiedby the PCF ID. If the PCF 135 identified by the PCF ID may not be used(e.g. no response from the PCF 135) or if there is no PCF ID receivedfrom the old AMF 155, the AMF 155 may select 925 a PCF 135.

In an example, the new AMF 155 may perform a policy associationestablishment 930 during registration procedure. If the new AMF 155contacts the PCF 135 identified by the (V-)PCF ID received duringinter-AMF 155 mobility, the new AMF 155 may include the PCF-ID in theNpcf_AMPolicyControl Get operation. If the AMF 155 notifies the mobilityrestrictions (e.g. UE 100 location) to the PCF 135 for adjustment, or ifthe PCF 135 updates the mobility restrictions itself due to someconditions (e.g. application in use, time and date), the PCF 135 mayprovide the updated mobility restrictions to the AMF 155.

In an example, the PCF 135 may invoke Namf_EventExposure_Subscribeservice operation 935 for UE 100 event subscription.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext 936. In an example, the AMF 155 mayinvoke the Nsmf_PDUSession_UpdateSMContext if the PDU session(s) to bere-activated is included in the registration request. The AMF 155 maysend Nsmf_PDUSession_UpdateSMContext request to SMF 160(s) associatedwith the PDU session(s) to activate user plane connections of the PDUsession(s). The SMF 160 may decide to trigger e.g. the intermediate UPF110 insertion, removal or change of PSA. In the case that theintermediate UPF 110 insertion, removal, or relocation is performed forthe PDU session(s) not included in PDU session(s) to be re-activated,the procedure may be performed without N11 and N2 interactions to updatethe N3 user plane between (R)AN 105 and 5GC. The AMF 155 may invoke theNsmf_PDUSession_ReleaseSMContext service operation towards the SMF 160if any PDU session status indicates that it is released at the UE 100.The AMF 155 may invoke the Nsmf_PDUSession_ReleaseSMContext serviceoperation towards the SMF 160 in order to release any network resourcesrelated to the PDU session.

In an example, the new AMF 155155 may send to a N3IWF an N2 AMF 155mobility request 940. If the AMF 155 has changed, the new AMF 155 maycreate an NGAP UE 100 association towards the N3IWF to which the UE 100is connected. In an example, the N3IWF may respond to the new AMF 155with an N2 AMF 155 mobility response 940.

In an example, the new AMF 155 may send to the UE 100 a registrationaccept 955 (comprising: 5G-GUTI, registration area, mobilityrestrictions, PDU session status, allowed NSSAI, [mapping of allowedNSSAI], periodic registration update timer, LADN information andaccepted MICO mode, IMS voice over PS session supported indication,emergency service support indicator, and/or the like). In an example,the AMF 155 may send the registration accept message to the UE 100indicating that the registration request has been accepted. 5G-GUTI maybe included if the AMF 155 allocates a new 5G-GUTI. If the AMF 155allocates a new registration area, it may send the registration area tothe UE 100 via registration accept message 955. If there is noregistration area included in the registration accept message, the UE100 may consider the old registration area as valid. In an example,mobility restrictions may be included in case mobility restrictions mayapply for the UE 100 and registration type may not be emergencyregistration. The AMF 155 may indicate the established PDU sessions tothe UE 100 in the PDU session status. The UE 100 may remove locally anyinternal resources related to PDU sessions that are not marked asestablished in the received PDU session status. In an example, when theUE 100 is connected to the two AMF 155 belonging to different PLMN via3GPP access and non-3GPP access then the UE 100 may remove locally anyinternal resources related to the PDU session of the current PLMN thatare not marked as established in received PDU session status. If the PDUsession status information was in the registration request, the AMF 155may indicate the PDU session status to the UE. The mapping of allowedNSSAI may be the mapping of one or more S-NSSAI of the allowed NSSAI tothe S-NSSAIs of the configured NSSAI for the HPLMN. The AMF 155 mayinclude in the registration accept message 955 the LADN information forLADNs that are available within the registration area determined by theAMF 155 for the UE. If the UE 100 included MICO mode in the request,then AMF 155 may respond whether MICO mode may be used. The AMF 155 mayset the IMS voice over PS session supported Indication. In an example,in order to set the IMS voice over PS session supported indication, theAMF 155 may perform a UE/RAN radio information and compatibility requestprocedure to check the compatibility of the UE 100 and RAN radiocapabilities related to IMS voice over PS. In an example, the emergencyservice support indicator may inform the UE 100 that emergency servicesare supported, e.g., the UE 100 may request PDU session for emergencyservices. In an example, the handover restriction list and UE-AMBR maybe provided to NG-RAN by the AMF 155.

In an example, the UE 100 may send to the new AMF 155 a registrationcomplete 960 message. In an example, the UE 100 may send theregistration complete message 960 to the AMF 155 to acknowledge that anew 5G-GUTI may be assigned. In an example, when information about thePDU session(s) to be re-activated is not included in the registrationrequest, the AMF 155 may release the signaling connection with the UE100. In an example, when the follow-on request is included in theregistration request, the AMF 155 may not release the signalingconnection after the completion of the registration procedure. In anexample, if the AMF 155 is aware that some signaling is pending in theAMF 155 or between the UE 100 and the 5GC, the AMF 155 may not releasethe signaling connection after the completion of the registrationprocedure.

As depicted in example FIG. 10 and FIG. 11, a service request proceduree.g., a UE 100 triggered service request procedure may be used by a UE100 in CM-IDLE state to request the establishment of a secure connectionto an AMF 155. FIG. 11 is continuation of FIG. 10 depicting the servicerequest procedure. The service request procedure may be used to activatea user plane connection for an established PDU session. The servicerequest procedure may be triggered by the UE 100 or the 5GC, and may beused when the UE 100 is in CM-IDLE and/or in CM-CONNECTED and may allowselectively to activate user plane connections for some of theestablished PDU sessions.

In an example, a UE 100 in CM IDLE state may initiate the servicerequest procedure to send uplink signaling messages, user data, and/orthe like, as a response to a network paging request, and/or the like. Inan example, after receiving the service request message, the AMF 155 mayperform authentication. In an example, after the establishment ofsignaling connection to the AMF 155, the UE 100 or network may sendsignaling messages, e.g. PDU session establishment from the UE 100 to aSMF 160, via the AMF 155.

In an example, for any service request, the AMF 155 may respond with aservice accept message to synchronize PDU session status between the UE100 and network. The AMF 155 may respond with a service reject messageto the UE 100, if the service request may not be accepted by thenetwork. The service reject message may include an indication or causecode requesting the UE 100 to perform a registration update procedure.In an example, for service request due to user data, network may takefurther actions if user plane connection activation may not besuccessful. In an example FIG. 10 and FIG. 11, more than one UPF, e.g.,old UPF 110-2 and PDU session Anchor PSA UPF 110-3 may be involved.

In an example, the UE 100 may send to a (R)AN 105 an AN messagecomprising AN parameters, mobility management, MM NAS service request1005 (e.g., list of PDU sessions to be activated, list of allowed PDUsessions, security parameters, PDU session status, and/or the like),and/or the like. In an example, the UE 100 may provide the list of PDUsessions to be activated when the UE 100 may re-activate the PDUsession(s). The list of allowed PDU sessions may be provided by the UE100 when the service request may be a response of a paging or a NASnotification, and may identify the PDU sessions that may be transferredor associated to the access on which the service request may be sent. Inan example, for the case of NG-RAN, the AN parameters may includeselected PLMN ID, and an establishment cause. The establishment causemay provide the reason for requesting the establishment of an RRCconnection. The UE 100 may send NAS service request message towards theAMF 155 encapsulated in an RRC message to the RAN 105.

In an example, if the service request may be triggered for user data,the UE 100 may identify, using the list of PDU sessions to be activated,the PDU session(s) for which the UP connections are to be activated inthe NAS service request message. If the service request may be triggeredfor signaling, the UE 100 may not identify any PDU session(s). If thisprocedure may be triggered for paging response, and/or the UE 100 mayhave at the same time user data to be transferred, the UE 100 mayidentify the PDU session(s) whose UP connections may be activated in MMNAS service request message, by the list of PDU sessions to beactivated.

In an example, if the service request over 3GPP access may be triggeredin response to a paging indicating non-3GPP access, the NAS servicerequest message may identify in the list of allowed PDU sessions thelist of PDU sessions associated with the non-3GPP access that may bere-activated over 3GPP. In an example, the PDU session status mayindicate the PDU sessions available in the UE 100. In an example, the UE100 may not trigger the service request procedure for a PDU sessioncorresponding to a LADN when the UE 100 may be outside the area ofavailability of the LADN. The UE 100 may not identify such PDUsession(s) in the list of PDU sessions to be activated if the servicerequest may be triggered for other reasons.

In an example, the (R)AN 105 may send to AMF 155 an N2 Message 1010(e.g., a service request) comprising N2 parameters, MM NAS servicerequest, and/or the like. The AMF 155 may reject the N2 message if itmay not be able to handle the service request. In an example, if NG-RANmay be used, the N2 parameters may include the 5G-GUTI, selected PLMNID, location information, RAT type, establishment cause, and/or thelike. In an example, the 5G-GUTI may be obtained in RRC procedure andthe (R)AN 105 may select the AMF 155 according to the 5G-GUTI. In anexample, the location information and RAT type may relate to the cell inwhich the UE 100 may be camping. In an example, based on the PDU sessionstatus, the AMF 155 may initiate PDU session release procedure in thenetwork for the PDU sessions whose PDU session ID(s) may be indicated bythe UE 100 as not available.

In an example, if the service request was not sent integrity protectedor integrity protection verification failed, the AMF 155 may initiate aNAS authentication/security procedure 1015.

In an example, if the UE 100 triggers the service request to establish asignaling connection, upon successful establishment of the signalingconnection, the UE 100 and the network may exchange NAS signaling.

In an example the AMF 155 may send to the SMF 160 a PDU session updatecontext request 1020 e.g., Nsmf_PDUSession_UpdateSMContext requestcomprising PDU session ID(s), Cause(s), UE 100 location information,access type, and/or the like.

In an example, the Nsmf_PDUSession_UpdateSMContext request may beinvoked by the AMF 155 if the UE 100 may identify PDU session(s) to beactivated in the NAS service request message. In an example, theNsmf_PDUSession_UpdateSMContext request may be triggered by the SMF 160wherein the PDU session(s) identified by the UE 100 may correlate toother PDU session ID(s) than the one triggering the procedure. In anexample, the Nsmf_PDUSession_UpdateSMContext request may be triggered bythe SMF 160 wherein the current UE 100 location may be outside the areaof validity for the N2 information provided by the SMF 160 during anetwork triggered service request procedure. The AMF 155 may not sendthe N2 information provided by the SMF 160 during the network triggeredservice request procedure.

In an example, the AMF 155 may determine the PDU session(s) to beactivated and may send an Nsmf_PDUSession_UpdateSMContext request to SMF160(s) associated with the PDU session(s) with cause set to indicateestablishment of user plane resources for the PDU session(s).

In an example, if the procedure may be triggered in response to pagingindicating non-3GPP access, and the list of allowed PDU sessionsprovided by the UE 100 may not include the PDU session for which the UE100 was paged, the AMF 155 may notify the SMF 160 that the user planefor the PDU session may not be re-activated. The service requestprocedure may succeed without re-activating the user plane of any PDUsessions, and the AMF 155 may notify the UE 100.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) keep thePDU session, may reject the activation of user plane connection for thePDU session and may inform the AMF 155. In an example, if the proceduremay be triggered by a network triggered service request, the SMF 160 maynotify the UPF 110 that originated the data notification to discarddownlink data for the PDU sessions and/or to not provide further datanotification messages. The SMF 160 may respond to the AMF 155 with anappropriate reject cause and the user plane activation of PDU sessionmay be stopped.

In an example, if the PDU session ID may correspond to a LADN and theSMF 160 may determine that the UE 100 may be outside the area ofavailability of the LADN based on the UE 100 location reporting from theAMF 155, the SMF 160 may decide to (based on local policies) release thePDU session. The SMF 160 may locally release the PDU session and mayinform the AMF 155 that the PDU session may be released. The SMF 160 mayrespond to the AMF 155 with an appropriate reject cause and the userplane Activation of PDU session may be stopped.

In an example, if the UP activation of the PDU session may be acceptedby the SMF 160, based on the location info received from the AMF 155,the SMF 160 may check the UPF 110 Selection 1025 Criteria (e.g., sliceisolation requirements, slice coexistence requirements, UPF's 110dynamic load, UPF's 110 relative static capacity among UPFs supportingthe same DNN, UPF 110 location available at the SMF 160, UE 100 locationinformation, Capability of the UPF 110 and the functionality requiredfor the particular UE 100 session. In an example, an appropriate UPF 110may be selected by matching the functionality and features required fora UE 100, DNN, PDU session type (i.e. IPv4, IPv6, ethernet type orunstructured type) and if applicable, the static IP address/prefix, SSCmode selected for the PDU session, UE 100 subscription profile in UDM140, DNAI as included in the PCC rules, local operator policies,S-NSSAI, access technology being used by the UE 100, UPF 110 logicaltopology, and/or the like), and may determine to perform one or more ofthe following: continue using the current UPF(s); may select a newintermediate UPF 110 (or add/remove an intermediate UPF 110), if the UE100 has moved out of the service area of the UPF 110 that was previouslyconnecting to the (R)AN 105, while maintaining the UPF(s) acting as PDUsession anchor; may trigger re-establishment of the PDU session toperform relocation/reallocation of the UPF 110 acting as PDU sessionanchor, e.g. the UE 100 has moved out of the service area of the anchorUPF 110 which is connecting to RAN 105.

In an example, the SMF 160 may send to the UPF 110 (e.g., newintermediate UPF 110) an N4 session establishment request 1030. In anexample, if the SMF 160 may select a new UPF 110 to act as intermediateUPF 110-2 for the PDU session, or if the SMF 160 may select to insert anintermediate UPF 110 for a PDU session which may not have anintermediate UPF 110-2, an N4 session establishment request 1030 messagemay be sent to the new UPF 110, providing packet detection, dataforwarding, enforcement and reporting rules to be installed on the newintermediate UPF. The PDU session anchor addressing information (on N9)for this PDU session may be provided to the intermediate UPF 110-2.

In an example, if a new UPF 110 is selected by the SMF 160 to replacethe old (intermediate) UPF 110-2, the SMF 160 may include a dataforwarding indication. The data forwarding indication may indicate tothe UPF 110 that a second tunnel endpoint may be reserved for bufferedDL data from the old I-UPF.

In an example, the new UPF 110 (intermediate) may send to SMF 160 an N4session establishment response message 1030. In case the UPF 110 mayallocate CN tunnel info, the UPF 110 may provide DL CN tunnel info forthe UPF 110 acting as PDU session anchor and UL CN tunnel info (e.g., CNN3 tunnel info) to the SMF 160. If the data forwarding indication may bereceived, the new (intermediate) UPF 110 acting as N3 terminating pointmay send DL CN tunnel info for the old (intermediate) UPF 110-2 to theSMF 160. The SMF 160 may start a timer, to release the resource in theold intermediate UPF 110-2.

In an example, if the SMF 160 may selects a new intermediate UPF 110 forthe PDU session or may remove the old I-UPF 110-2, the SMF 160 may sendN4 session modification request message 1035 to PDU session anchor, PSAUPF 110-3, providing the data forwarding indication and DL tunnelinformation from new intermediate UPF 110.

In an example, if the new intermediate UPF 110 may be added for the PDUsession, the (PSA) UPF 110-3 may begin to send the DL data to the newI-UPF 110 as indicated in the DL tunnel information.

In an example, if the service request may be triggered by the network,and the SMF 160 may remove the old I-UPF 110-2 and may not replace theold I-UPF 110-2 with the new I-UPF 110, the SMF 160 may include the dataforwarding indication in the request. The data forwarding indication mayindicate to the (PSA) UPF 110-3 that a second tunnel endpoint may bereserved for buffered DL data from the old I-UPF 110-2. In this case,the PSA UPF 110-3 may begin to buffer the DL data it may receive at thesame time from the N6 interface.

In an example, the PSA UPF 110-3 (PSA) may send to the SMF 160 an N4session modification response 1035. In an example, if the dataforwarding indication may be received, the PSA UPF 110-3 may become asN3 terminating point and may send CN DL tunnel info for the old(intermediate) UPF 110-2 to the SMF 160. The SMF 160 may start a timer,to release the resource in old intermediate UPF 110-2 if there is one.

In an example, the SMF 160 may send to the old UPF 110-2 an N4 sessionmodification request 1045 (e.g., may comprise new UPF 110 address, newUPF 110 DL tunnel ID, and/or the like). In an example, if the servicerequest may be triggered by the network, and/or the SMF 160 may removethe old (intermediate) UPF 110-2, the SMF 160 may send the N4 sessionmodification request message to the old (intermediate) UPF 110-2, andmay provide the DL tunnel information for the buffered DL data. If theSMF 160 may allocate new I-UPF 110, the DL tunnel information is fromthe new (intermediate) UPF 110 may act as N3 terminating point. If theSMF 160 may not allocate a new I-UPF 110, the DL tunnel information maybe from the new UPF 110 (PSA) 110-3 acting as N3 terminating point. TheSMF 160 may start a timer to monitor the forwarding tunnel. In anexample, the old (intermediate) UPF 110-2 may send N4 sessionmodification response message to the SMF 160.

In an example, if the I-UPF 110-2 may be relocated and forwarding tunnelwas established to the new I-UPF 110, the old (intermediate) UPF 110-2may forward its buffered data to the new (intermediate) UPF 110 actingas N3 terminating point. In an example, if the old I-UPF 110-2 may beremoved and the new I-UPF 110 may not be assigned for the PDU sessionand forwarding tunnel may be established to the UPF 110 (PSA) 110-3, theold (intermediate) UPF 110-2 may forward its buffered data to the UPF110 (PSA) 110-3 acting as N3 terminating point.

In an example, the SMF 160 may send to the AMF 155 an N11 message 1060e.g., a Nsmf_PDUSession_UpdateSMContext response (comprising: N1 SMcontainer (PDU session ID, PDU session re-establishment indication), N2SM information (PDU session ID, QoS profile, CN N3 tunnel info,S-NSSAI), Cause), upon reception of the Nsmf_PDUSession_UpdateSMContextrequest with a cause including e.g., establishment of user planeresources. The SMF 160 may determine whether UPF 110 reallocation may beperformed, based on the UE 100 location information, UPF 110 servicearea and operator policies. In an example, for a PDU session that theSMF 160 may determine to be served by the current UPF 110, e.g., PDUsession anchor or intermediate UPF, the SMF 160 may generate N2 SMinformation and may send an Nsmf_PDUSession_UpdateSMContext response1060 to the AMF 155 to establish the user plane(s). The N2 SMinformation may contain information that the AMF 155 may provide to theRAN 105. In an example, for a PDU session that the SMF 160 may determineas requiring a UPF 110 relocation for PDU session anchor UPF, the SMF160 may reject the activation of UP of the PDU session by sendingNsmf_PDUSession_UpdateSMContext response that may contain N1 SMcontainer to the UE 100 via the AMF 155. The N1 SM container may includethe corresponding PDU session ID and PDU session re-establishmentindication.

Upon reception of the Namf_EventExposure_Notify from the AMF 155 to theSMF 160, with an indication that the UE 100 is reachable, if the SMF 160may have pending DL data, the SMF 160 may invoke theNamf_Communication_N1N2MessageTransfer service operation to the AMF 155to establish the user plane(s) for the PDU sessions. In an example, theSMF 160 may resume sending DL data notifications to the AMF 155 in caseof DL data.

In an example, the SMF 160 may send a message to the AMF 155 to rejectthe activation of UP of the PDU session by including a cause in theNsmf_PDUSession_UpdateSMContext response if the PDU session maycorrespond to a LADN and the UE 100 may be outside the area ofavailability of the LADN, or if the AMF 155 may notify the SMF 160 thatthe UE 100 may be reachable for regulatory prioritized service, and thePDU session to be activated may not for a regulatory prioritizedservice; or if the SMF 160 may decide to perform PSA UPF 110-3relocation for the requested PDU session.

In an example, the AMF 155 may send to the (R)AN 105 an N2 requestmessage 1065 (e.g., N2 SM information received from SMF 160, securitycontext, AMF 155 signaling connection ID, handover restriction list, MMNAS service accept, list of recommended cells/TAs/NG-RAN nodeidentifiers). In an example, the RAN 105 may store the security context,AMF 155 signaling connection Id, QoS information for the QoS flows ofthe PDU sessions that may be activated and N3 tunnel IDs in the UE 100RAN 105 context. In an example, the MM NAS service accept may includePDU session status in the AMF 155. If the activation of UP of a PDUsession may be rejected by the SMF 160, the MM NAS service accept mayinclude the PDU session ID and the reason why the user plane resourcesmay not be activated (e.g. LADN not available). Local PDU sessionrelease during the session request procedure may be indicated to the UE100 via the session Status.

In an example, if there are multiple PDU sessions that may involvemultiple SMF 160 s, the AMF 155 may not wait for responses from all SMF160 s before it may send N2 SM information to the UE 100. The AMF 155may wait for all responses from the SMF 160 s before it may send MM NASservice accept message to the UE 100.

In an example, the AMF 155 may include at least one N2 SM informationfrom the SMF 160 if the procedure may be triggered for PDU session userplane activation. AMF 155 may send additional N2 SM information from SMF160 s in separate N2 message(s) (e.g. N2 tunnel setup request), if thereis any. Alternatively, if multiple SMF 160 s may be involved, the AMF155 may send one N2 request message to (R)AN 105 after all theNsmf_PDUSession_UpdateSMContext response service operations from all theSMF 160 s associated with the UE 100 may be received. In such case, theN2 request message may include the N2 SM information received in one ormore of the Nsmf_PDUSession_UpdateSMContext response and PDU session IDto enable AMF 155 to associate responses to relevant SMF 160.

In an example, if the RAN 105 (e.g., NG RAN) node may provide the listof recommended cells/TAs/NG-RAN node identifiers during the AN releaseprocedure, the AMF 155 may include the information from the list in theN2 request. The RAN 105 may use this information to allocate the RAN 105notification area when the RAN 105 may decide to enable RRC inactivestate for the UE 100.

If the AMF 155 may receive an indication, from the SMF 160 during a PDUsession establishment procedure that the UE 100 may be using a PDUsession related to latency sensitive services, for any of the PDUsessions established for the UE 100 and the AMF 155 has received anindication from the UE 100 that may support the CM-CONNECTED with RRCinactive state, then the AMF 155 may include the UE's RRC inactiveassistance information. In an example, the AMF 155 based on networkconfiguration, may include the UE's RRC inactive assistance information.

In an example, the (R)AN 105 may send to the UE 100 a message to performRRC connection reconfiguration 1070 with the UE 100 depending on the QoSinformation for all the QoS flows of the PDU sessions whose UPconnections may be activated and data radio bearers. In an example, theuser plane security may be established.

In an example, if the N2 request may include a MM NAS service acceptmessage, the RAN 105 may forward the MM NAS service accept to the UE100. The UE 100 may locally delete context of PDU sessions that may notbe available in 5GC.

In an example, if the N1 SM information may be transmitted to the UE 100and may indicate that some PDU session(s) may be re-established, the UE100 may initiate PDU session re-establishment for the PDU session(s)that may be re-established after the service request procedure may becomplete.

In an example, after the user plane radio resources may be setup, theuplink data from the UE 100 may be forwarded to the RAN 105. The RAN 105(e.g., NG-RAN) may send the uplink data to the UPF 110 address andtunnel ID provided.

In an example, the (R)AN 105 may send to the AMF 155 an N2 request Ack1105 (e.g., N2 SM information (comprising: AN tunnel info, list ofaccepted QoS flows for the PDU sessions whose UP connections areactivated, list of rejected QoS flows for the PDU sessions whose UPconnections are activated)). In an example, the N2 request message mayinclude N2 SM information(s), e.g. AN tunnel info. RAN 105 may respondN2 SM information with separate N2 message (e.g. N2 tunnel setupresponse). In an example, if multiple N2 SM information are included inthe N2 request message, the N2 request Ack may include multiple N2 SMinformation and information to enable the AMF 155 to associate theresponses to relevant SMF 160.

In an example, the AMF 155 may send to the SMF 160 aNsmf_PDUSession_UpdateSMContext request 1110 (N2 SM information (ANtunnel info), RAT type) per PDU session. If the AMF 155 may receive N2SM information (one or multiple) from the RAN 105, then the AMF 155 mayforward the N2 SM information to the relevant SMF 160. If the UE 100time zone may change compared to the last reported UE 100 Time Zone thenthe AMF 155 may include the UE 100 time zone IE in theNsmf_PDUSession_UpdateSMContext request message.

In an example, if dynamic PCC is deployed, the SMF 160 may initiatenotification about new location information to the PCF 135 (ifsubscribed) by invoking an event exposure notification operation (e.g.,a Nsmf_EventExposure_Notify service operation). The PCF 135 may provideupdated policies by invoking a policy control update notificationmessage 1115 (e.g., a Npcf_SMPolicyControl_UpdateNotify operation).

In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110 for the PDU session, the SMF 160 may initiates anN4 session modification procedure 1120 to the new I-UPF 110 and mayprovide AN tunnel info. The downlink data from the new I-UPF 110 may beforwarded to RAN 105 and UE 100. In an example, the UPF 110 may send tothe SMF 160, an N4 session modification response 1120. In an example,the SMF 160 may send to the AMF 155, an Nsmf_PDUSession_UpdateSMContextresponse 1140.

In an example, if forwarding tunnel may be established to the new I-UPF110 and if the timer SMF 160 set for forwarding tunnel may be expired,the SMF 160 may sends N4 session modification request 1145 to new(intermediate) UPF 110 acting as N3 terminating point to release theforwarding tunnel. In an example, the new (intermediate) UPF 110 maysend to the SMF 160 an N4 session modification response 1145. In anexample, the SMF 160 may send to the PSA UPF 110-3 an N4 sessionmodification request 1150, or N4 session release request. In an example,if the SMF 160 may continue using the old UPF 110-2, the SMF 160 maysend an N4 session modification request 1155, providing AN tunnel info.In an example, if the SMF 160 may select a new UPF 110 to act asintermediate UPF 110, and the old UPF 110-2 may not be PSA UPF 110-3,the SMF 160 may initiate resource release, after timer expires, bysending an N4 session release request (release cause) to the oldintermediate UPF 110-2.

In an example, the old intermediate UPF 110-2 may send to the SMF 160 anN4 session modification response or N4 session release response 1155.The old UPF 110-2 may acknowledge with the N4 session modificationresponse or N4 session release response message to confirm themodification or release of resources. The AMF 155 may invoke theNamf_EventExposure_Notify service operation to notify the mobilityrelated events, after this procedure may complete, towards the NFs thatmay have subscribed for the events. In an example, the AMF 155 mayinvoke the Namf_EventExposure_Notify towards the SMF 160 if the SMF 160had subscribed for UE 100 moving into or out of area of interest and ifthe UE's current location may indicate that it may be moving into ormoving outside of the area of interest subscribed, or if the SMF 160 hadsubscribed for LADN DNN and if the UE 100 may be moving into or outsideof an area where the LADN is available, or if the UE 100 may be in MICOmode and the AMF 155 had notified an SMF 160 of the UE 100 beingunreachable and that SMF 160 may not send DL data notifications to theAMF 155, and the AMF 155 may informs the SMF 160 that the UE 100 isreachable, or if the SMF 160 had subscribed for UE 100 reachabilitystatus, then the AMF 155 may notify the UE 100 reachability.

An example PDU session establishment procedure depicted in FIG. 12 andFIG. 13. In an example embodiment, when the PDU session establishmentprocedure may be employed, the UE 100 may send to the AMF 155 a NASMessage 1205 (or a SM NAS message) comprising NSSAI, S-NSSAI (e.g.,requested S-NSSAI, allowed S-NSSAI, subscribed S-NSSAI, and/or thelike), DNN, PDU session ID, request type, old PDU session ID, N1 SMcontainer (PDU session establishment request), and/or the like. In anexample, the UE 100, in order to establish a new PDU session, maygenerate a new PDU session ID. In an example, when emergency service maybe required and an emergency PDU session may not already be established,the UE 100 may initiate the UE 100 requested PDU session establishmentprocedure with a request type indicating emergency request. In anexample, the UE 100 may initiate the UE 100 requested PDU sessionestablishment procedure by the transmission of the NAS messagecontaining a PDU session establishment request within the N1 SMcontainer. The PDU session establishment request may include a PDU type,SSC mode, protocol configuration options, and/or the like. In anexample, the request type may indicate initial request if the PDUsession establishment is a request to establish the new PDU session andmay indicate existing PDU session if the request refers to an existingPDU session between 3GPP access and non-3GPP access or to an existingPDN connection in EPC. In an example, the request type may indicateemergency request if the PDU session establishment may be a request toestablish a PDU session for emergency services. The request type mayindicate existing emergency PDU session if the request refers to anexisting PDU session for emergency services between 3GPP access andnon-3GPP access. In an example, the NAS message sent by the UE 100 maybe encapsulated by the AN in a N2 message towards the AMF 155 that mayinclude user location information and access technology typeinformation. In an example, the PDU session establishment requestmessage may contain SM PDU DN request container containing informationfor the PDU session authorization by the external DN. In an example, ifthe procedure may be triggered for SSC mode 3 operation, the UE 100 mayinclude the old PDU session ID which may indicate the PDU session ID ofthe on-going PDU session to be released, in the NAS message. The old PDUsession ID may be an optional parameter which may be included in thiscase. In an example, the AMF 155 may receive from the AN the NAS message(e.g., NAS SM message) together with user location information (e.g.cell ID in case of the RAN 105). In an example, the UE 100 may nottrigger a PDU session establishment for a PDU session corresponding to aLADN when the UE 100 is outside the area of availability of the LADN.

In an example, the AMF 155 may determine that the NAS message or the SMNAS message may correspond to the request for the new PDU session basedon that request type indicates initial request and that the PDU sessionID may not be used for any existing PDU session(s) of the UE 100. If theNAS message does not contain an S-NSSAI, the AMF 155 may determine adefault S-NSSAI for the requested PDU session either according to the UE100 subscription, if it may contain only one default S-NSSAI, or basedon operator policy. In an example, the AMF 155 may perform SMF 160selection 1210 and select an SMF 160. If the request type may indicateinitial request or the request may be due to handover from EPS, the AMF155 may store an association of the S-NSSAI, the PDU session ID and aSMF 160 ID. In an example, if the request type is initial request and ifthe old PDU session ID indicating the existing PDU session may becontained in the message, the AMF 155 may select the SMF 160 and maystore an association of the new PDU session ID and the selected SMF 160ID.

In an example, the AMF 155 may send to the SMF 160, an N11 message 1215,e.g., Nsmf_PDUSession_CreateSMContext request (comprising: SUPI or PEI,DNN, S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container(PDU session establishment request), user location information, accesstype, PEI, GPSI), or Nsmf_PDUSession_UpdateSMContext request (SUPI, DNN,S-NSSAI, PDU session ID, AMF 155 ID, request type, N1 SM container (PDUsession establishment request), user location information, access type,RAT type, PEI). In an example, if the AMF 155 may not have anassociation with the SMF 160 for the PDU session ID provided by the UE100 (e.g. when request type indicates initial request), the AMF 155 mayinvoke the Nsmf_PDUSession_CreateSMContext request, but if the AMF 155already has an association with an SMF 160 for the PDU session IDprovided by the UE 100 (e.g. when request type indicates existing PDUsession), the AMF 155 may invoke the Nsmf_PDUSession_UpdateSMContextrequest. In an example, the AMF 155 ID may be the UE's GUAMI whichuniquely identifies the AMF 155 serving the UE 100. The AMF 155 mayforward the PDU session ID together with the N1 SM container containingthe PDU session establishment request received from the UE 100. The AMF155 may provide the PEI instead of the SUPI when the UE 100 hasregistered for emergency services without providing the SUPI. In casethe UE 100 has registered for emergency services but has not beenauthenticated, the AMF 155 may indicate that the SUPI has not beenauthenticated.

In an example, if the request type may indicate neither emergencyrequest nor existing emergency PDU session and, if the SMF 160 has notyet registered and subscription data may not be available, the SMF 160may register with the UDM 140, and may retrieve subscription data 1225and subscribes to be notified when subscription data may be modified. Inan example, if the request type may indicate existing PDU session orexisting emergency PDU session, the SMF 160 may determine that therequest may be due to handover between 3GPP access and non-3GPP accessor due to handover from EPS. The SMF 160 may identify the existing PDUsession based on the PDU session ID. The SMF 160 may not create a new SMcontext but instead may update the existing SM context and may providethe representation of the updated SM context to the AMF 155 in theresponse. if the request type may be initial request and if the old PDUsession ID may be included in Nsmf_PDUSession_CreateSMContext request,the SMF 160 may identify the existing PDU session to be released basedon the old PDU session ID.

In an example, the SMF 160 may send to the AMF 155, the N11 messageresponse 1220, e.g., either a PDU session create/update response,Nsmf_PDUSession_CreateSMContext response 1220 (cause, SM context ID orN1 SM container (PDU session reject(cause))) or anNsmf_PDUSession_UpdateSMContext response.

In an example, if the SMF 160 may perform secondaryauthorization/authentication 1230 during the establishment of the PDUsession by a DN-AAA server, the SMF 160 may select a UPF 110 and maytrigger a PDU session establishment authentication/authorization.

In an example, if the request type may indicate initial request, the SMF160 may select an SSC mode for the PDU session. The SMF 160 may selectone or more UPFs as needed. In case of PDU type IPv4 or IPv6, the SMF160 may allocate an IP address/prefix for the PDU session. In case ofPDU type IPv6, the SMF 160 may allocate an interface identifier to theUE 100 for the UE 100 to build its link-local address. For UnstructuredPDU type the SMF 160 may allocate an IPv6 prefix for the PDU session andN6 point-to-point tunneling (based on UDP/IPv6).

In an example, if dynamic PCC is deployed, the may SMF 160 performs PCF135 selection 1235. If the request type indicates existing PDU sessionor existing emergency PDU session, the SMF 160 may use the PCF 135already selected for the PDU session. If dynamic PCC is not deployed,the SMF 160 may apply local policy.

In an example, the SMF 160 may perform a session management policyestablishment procedure 1240 to establish a PDU session with the PCF 135and may get the default PCC Rules for the PDU session. The GPSI may beincluded if available at the SMF 160. If the request type in 1215indicates existing PDU session, the SMF 160 may notify an eventpreviously subscribed by the PCF 135 by a session management policymodification procedure and the PCF 135 may update policy information inthe SMF 160. The PCF 135 may provide authorized session-AMBR and theauthorized 5QI and ARP to SMF 160. The PCF 135 may subscribe to the IPallocation/release event in the SMF 160 (and may subscribe otherevents).

In an example, the PCF 135, based on the emergency DNN, may set the ARPof the PCC rules to a value that may be reserved for emergency services.

In an example, if the request type in 1215 indicates initial request,the SMF 160 may select an SSC mode for the PDU session. The SMF 160 mayselect 1245 one or more UPFs as needed. In case of PDU type IPv4 orIPv6, the SMF 160 may allocate an IP address/prefix for the PDU session.In case of PDU type IPv6, the SMF 160 may allocate an interfaceidentifier to the UE 100 for the UE 100 to build its link-local address.For unstructured PDU type the SMF 160 may allocate an IPv6 prefix forthe PDU session and N6 point-to-point tunneling (e.g., based onUDP/IPv6). In an example, for Ethernet PDU type PDU session, neither aMAC nor an IP address may be allocated by the SMF 160 to the UE 100 forthis PDU session.

In an example, if the request type in 1215 is existing PDU session, theSMF 160 may maintain the same IP address/prefix that may be allocated tothe UE 100 in the source network.

In an example, if the request type in 1215 indicates existing PDUsession referring to an existing PDU session moved between 3GPP accessand non-3GPP access, the SMF 160 may maintain the SSC mode of the PDUsession, e.g., the current PDU session Anchor and IP address. In anexample, the SMF 160 may trigger e.g. new intermediate UPF 110 insertionor allocation of a new UPF 110. In an example, if the request typeindicates emergency request, the SMF 160 may select 1245 the UPF 110 andmay select SSC mode 1.

In an example, the SMF 160 may perform a session management policymodification 1250 procedure to report some event to the PCF 135 that haspreviously subscribed. If request type is initial request and dynamicPCC is deployed and PDU type is IPv4 or IPv6, the SMF 160 may notify thePCF 135 (that has previously subscribed) with the allocated UE 100 IPaddress/prefix.

In an example, the PCF 135 may provide updated policies to the SMF 160.The PCF 135 may provide authorized session-AMBR and the authorized 5QIand ARP to the SMF 160.

In an example, if request type indicates initial request, the SMF 160may initiate an N4 session establishment procedure 1255 with theselected UPF 110. The SMF 160 may initiate an N4 session modificationprocedure with the selected UPF 110. In an example, the SMF 160 may sendan N4 session establishment/modification request 1255 to the UPF 110 andmay provide packet detection, enforcement, reporting rules, and/or thelike to be installed on the UPF 110 for this PDU session. If CN tunnelinfo is allocated by the SMF 160, the CN tunnel info may be provided tothe UPF 110. If the selective user plane deactivation is required forthis PDU session, the SMF 160 may determine the Inactivity Timer and mayprovide it to the UPF 110. In an example, the UPF 110 may acknowledgesby sending an N4 session establishment/modification response 1255. If CNtunnel info is allocated by the UPF, the CN tunnel info may be providedto SMF 160. In an example, if multiple UPFs are selected for the PDUsession, the SMF 160 may initiate N4 session establishment/modificationprocedure 1255 with one or more UPF 110 of the PDU session.

In an example, the SMF 160 may send to the AMF 155 anNamf_Communication_N1N2MessageTransfer 1305 message (comprising PDUsession ID, access type, N2 SM information (PDU session ID, QFI(s), QoSprofile(s), CN tunnel info, S-NSSAI, session-AMBR, PDU session type,and/or the like), N1 SM container (PDU session establishment accept (QoSRule(s), selected SSC mode, S-NSSAI, allocated IPv4 address, interfaceidentifier, session-AMBR, selected PDU session type, and/or the like))).In case of multiple UPFs are used for the PDU session, the CN tunnelinfo may comprise tunnel information related with the UPF 110 thatterminates N3. In an example, the N2 SM information may carryinformation that the AMF 155 may forward to the (R)AN 105 (e.g., the CNtunnel info corresponding to the core network address of the N3 tunnelcorresponding to the PDU session, one or multiple QoS profiles and thecorresponding QFIs may be provided to the (R)AN 105, the PDU session IDmay be used by AN signaling with the UE 100 to indicate to the UE 100the association between AN resources and a PDU session for the UE100,and/or the like). In an example, a PDU session may be associated to anS-NSSAI and a DNN. In an example, the N1 SM container may contain thePDU session establishment accept that the AMF 155 may provide to the UE100. In an example, multiple QoS rules and QoS profiles may be includedin the PDU session establishment accept within the N1 SM and in the N2SM information. In an example, theNamf_Communication_N1N2MessageTransfer 1305 may further comprise the PDUsession ID and information allowing the AMF 155 to know which accesstowards the UE 100 to use.

In an example, the AMF 155 may send to the (R)AN105 an N2 PDU sessionrequest 1310 (comprising N2 SM information, NAS message (PDU session ID,N1 SM container (PDU session establishment accept, and/or the like))).In an example, the AMF 155 may send the NAS message 1310 that maycomprise PDU session ID and PDU session establishment accept targeted tothe UE 100 and the N2 SM information received from the SMF 160 withinthe N2 PDU session request 1310 to the (R)AN 105.

In an example, the (R)AN 105 may issue AN specific signaling exchange1315 with the UE 100 that may be related with the information receivedfrom SMF 160. In an example, in case of a 3GPP RAN 105, an RRCconnection reconfiguration procedure may take place with the UE 100 toestablish the necessary RAN 105 resources related to the QoS Rules forthe PDU session request 1310. In an example, (R)AN 105 may allocate(R)AN 105 N3 tunnel information for the PDU session. In case of dualconnectivity, the master RAN 105 node may assign some (zero or more)QFIs to be setup to a master RAN 105 node and others to the secondaryRAN 105 node. The AN tunnel info may comprise a tunnel endpoint for oneor more involved RAN 105 nodes, and the QFIs assigned to one or moretunnel endpoints. A QFI may be assigned to either the master RAN 105node or the secondary RAN 105 node. In an example, (R)AN 105 may forwardthe NAS message 1310 (PDU session ID, N1 SM container (PDU sessionestablishment accept)) to the UE 100. The (R)AN 105 may provide the NASmessage to the UE 100 if the necessary RAN 105 resources are establishedand the allocation of (R)AN 105 tunnel information are successful.

In an example, the N2 PDU session response 1320 may comprise a PDUsession ID, cause, N2 SM information (PDU session ID, AN tunnel info,list of accepted/rejected QFI(s)), and/or the like. In an example, theAN tunnel info may correspond to the access network address of the N3tunnel corresponding to the PDU session.

In an example, the AMF 155 may forward the N2 SM information receivedfrom (R)AN 105 to the SMF 160 via a Nsmf_PDUSession_UpdateSMContextrequest 1330 (comprising: N2 SM information, request type, and/or thelike). In an example, if the list of rejected QFI(s) is included in N2SM information, the SMF 160 may release the rejected QFI(s) associatedQoS profiles.

In an example, the SMF 160 may initiate an N4 session modificationprocedure 1335 with the UPF110. The SMF 160 may provide AN tunnel infoto the UPF 110 as well as the corresponding forwarding rules. In anexample, the UPF 110 may provide an N4 session modification response1335 to the SMF 160.

In an example, the SMF 160 may send to the AMF 155 anNsmf_PDUSession_UpdateSMContext response 1340 (Cause). In an example,the SMF 160 may subscribe to the UE 100 mobility event notification fromthe AMF 155 (e.g. location reporting, UE 100 moving into or out of areaof interest), after this step by invoking Namf_EventExposure_Subscribeservice operation. For LADN, the SMF 160 may subscribe to the UE 100moving into or out of LADN service area event notification by providingthe LADN DNN as an indicator for the area of interest. The AMF 155 mayforward relevant events subscribed by the SMF 160.

In an example, the SMF 160 may send to the AMF 155, aNsmf_PDUSession_SMContextStatusNotify (release) 1345. In an example, ifduring the procedure, any time the PDU session establishment is notsuccessful, the SMF 160 may inform the AMF 155 by invokingNsmf_PDUSession_SMContextStatusNotify(release) 1345. The SMF 160 mayreleases any N4 session(s) created, any PDU session address if allocated(e.g. IP address) and may release the association with the PCF 135.

In an example, in case of PDU type IPv6, the SMF 160 may generate anIPv6 Router Advertisement 1350 and may send it to the UE 100 via N4 andthe UPF 110.

In an example, if the PDU session may not be established, the SMF 160may unsubscribe 1360 to the modifications of session managementsubscription data for the corresponding (SUPI, DNN, S-NSSAI), usingNudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI), if the SMF 160 is no morehandling a PDU session of the UE 100 for this (DNN, S-NSSAI). In anexample, if the PDU session may not be established, the SMF 160 mayderegister 1360 for the given PDU session using Nudm_UECM_Deregistration(SUPI, DNN, PDU session ID).

In an example, a wireless communication system (e.g., 5GS, 3GPP system,3GPP communication system, 4G, LTE, and/or the like) may support 5G LANcommunication. A 5GLAN group communication session may be identified bya tuple of S-NSSAI and/or DNN. In an example, the 5GLAN group may beidentified by a group identifier, VLAN ID, DNN, S-NSSAI, and/or thelike. In case of supporting VLAN tags for 5G LAN communications, the 5GLAN group communication session may be identified by a tuple of S-NSSAI,DNN and VLAN Tag. In an example, the 5G LAN group, 5G LAN groupcommunication session, and/or the like may be identified by anidentifier of a group (e.g., a group id, internal group id, externalgroup id, a group index, group information, and/or the like). In anexample, a PDU session, a PDU session establishment, and/or the like maybe employed for the 5G LAN group communication session. The PDU sessionestablishment may employ the tuple of S-NSSAI, DNN, a group id, and/orthe like. In an example, area restriction of the 5G LAN service may bedone by configuring a DNN as the LADN DNN with LADN service area (e.g.,a list of tracking areas, and/or the like). In an example, a UE mayconnect to a virtual network that may connect one or more UEs within thegroup as depicted in example FIG. 14. As depicted in Example FIG. 14,same SMF (one common SMF) may be employed for the group communicationsession. In an example, a data network may be employed for groupcommunication. In an example, a PDU session anchor UPF (PSA-UPF) may beemployed to transmission/sending/receiving/forwarding of 5G LANcommunication packets. The PSA-UPF may enforce group AMBR, group quota,individual UE's AMBR or QoS enforcement, and/or the like. The PSA-UPFmay be functionally/logically/physically collocated with an intermediateUPF (I-UPF). The SMF may manage/check/determine one or more establishedand/or activated PDU sessions.

In an example as depicted in FIG. 15, an admin user (e.g.,administrator, a UE which belongs to a 5GLAN admin group, and/or thelike) may request addition/deletion of a 5GLAN user group and add (ordelete) a member to the 5GLAN user group. A UE may belong to one or moregroups and the subscription data for the UE in a UDR may associate thesubscriber with groups. In an example, an internal group identifier inthe UDR may identify a group. A group management may be a managementfunctionality on manipulating the UDR records. For example, creating agroup with list of group members may be implemented as creating a recordof group subscription data. In an example, addition, adding or deletinga member in the group may be defined as adding or deleting a SUPI in thegroup subscription data. A domain may be a logical administrative areawithin which a member of the admin group may manage the user groups andtheir membership. A domain may be employed to refer a tenant (e.g., acustomer of 5G LAN service provided by an operator). A domain maycomprise a domain identifier, an admin group identifier, one or moregroup identifiers, and/or the like.

An example FIG. 15, depicts the relationship of domain, admin group anduser group for 5G LAN group. A domain may comprise an admin group andone or more user groups. A user in the admin group may manage the usergroup and membership of the admin/user group in the domain and manage(e.g., provision, activate, deactivate, and/or the like) the 5GLANcommunication session. A user may belong to one or more groups (e.g., auser 2 may be a member of admin group, a member of user group A.1 and amember of user group A.2 as depicted in example FIG. 15.

In an example embodiment as depicted in FIG. 16, an AF (e.g., an adminsubscriber, and/or the like) may request an NEF to activate a groupcommunication session. The request may comprise a UE identifier of therequestor, a requestor id, and/or the like with an authorizationinformation. The NEF may check if the requestor is authorized toactivate the group communication session. The NEF may retrieve a list ofthe UE identifiers of the group and may update the UE policy for one ormore UE(s) in the group. A UDR may notify a PCF for updating the policydata since the PCF subscribed the UDR on the change of the policy data.The PCF may initiate a UE policy delivery procedure e.g., delivery of aUE route selection policy (URSP). In order for the UE to establish thePDU session after the UE policy is delivered, the URSP may comprise apolicy enforcement parameter that may indicate a request forestablishment of the PDU session. The UE may receive the UE policy andif the UE policy includes the establishment request of the PDU session,the UE may perform a PDU session establishment procedure with theconfigured parameters as encoded as route selection components in theURSP rules.

In an example, for one to many communication in a virtual network group,during the UE policy delivery procedure, the SMF may allocate amulticast information, multicast address, and or the like for the group.The URSP may comprise the multicast address and the UE may be configuredto send data to the multicast address when determining to send data forthe group communication. The multicast information may further comprisea set of wireless device identifiers in a group, an identifier of thegroup, and/or the like.

In an example embodiment as depicted in FIG. 17, the AF (e.g., adminuser) may request the NEF to activate a group communication. Theprocedure may be based on a PDU session modification procedure. Therequest may comprise the UE identifier of the requestor with theauthorization information. The NEF may check if the requestor isauthorized to activate the group communication session. The NEF mayretrieve the list of the UE identifiers of the group and may update theUE policy for one or more UE(s) in the group. The UDR may notify the PCFfor updating the policy data since the PCF subscribed the UDR on thechange of the policy data. The PCF may perform the SM policy controlupdate notification procedure to deliver the update policy informationfor the established session for example, the addition of a VLAG TAG,and/or the like. The SMF may initiate the PDU session modificationprocedure to send the VLAN TAG, and/or the like to the UE.

In an example embodiment as depicted in FIG. 19, a group may be created,and group member UE-T and UE-R1 may be added into the group, and UE-T isauthorized to send one to many data to the members in the group. UE-Tmay initiate group specific PDU Session establishment request, includingthe requested S-NSSAI, group information, and/or the like. In anexample, the group information may be a group index, a group specificDNN information or group specific application server information, and/orthe like. After receiving the request from UE-T, the SMF may select theUPF1 as the serving UPF for the specific group and may assign addresses(e.g., multicast address) for one to many data communication based onthe S-NSSAI information and the group information. The SMF may sendsession establishment request to UPF1, including the allocated CN tunnelinformation on N3 interface. UPF1 may acknowledge by sending Sessionestablishment response message. The SMF may send a PDU Session Acceptmessage to the UE-T with the addresses, multicast address, and/or thelike for one to many data communication. In case of PDU Session TypeIPv4 or IPv6 or IPv4v6, the SMF may allocate an IP address/prefix forthe PDU Session. When UE-R2 is added into the group, UE-R2 may initiatePDU Session establishment request to the SMF, that may comprise S-NSSAIinformation and group information. The SMF may select UPF2 as theserving UPF for UE-R2 and may assign same addresses for one to many datacommunication based on the S-NSSAI information and group information,and may determines to establish the forwarding tunnel between UPF1serving UE-T and the UPF2. The SMF may send session establishmentrequest to UPF2, including the allocated CN tunnel information and theallocated addresses for one to many data communication. The CN tunnelinformation may comprise the UPF2 address of the tunnel between UPF1 andUPF2 and the UPF2 address of N3 tunnel. UPF2 may acknowledge by sendingSession establishment response message. The SMF may establish a groupforwarding tunnel between UPF1 and UPF2, and may provide the UPF2address of the tunnel between UPF1 and UPF2, as well as addresses forone to many data communication to UPF1. The SMF may associate theforwarding tunnel, addresses for one to many data communication and PDUSession for UE-T to group path and may provide the group forwarding pathto UPF1. The SMF may send a PDU Session Accept to UE-R2 with theaddresses for one to many data communication. In case of PDU SessionType IPv4 or IPv6 or IPv4v6, the SMF may allocate an IP address/prefixfor the PDU Session, and the address/prefix is the group specific forUE-R2. If there is existing PDU Session for another group for UE-R2, theexisting PDU Session may be re-used for the newly joined group, e.g.,multiple groups may share one PDU Session for the receiving member inthe group. The UE-T may send the group data to the UPF1, UPF1 maydetermine the receiving UE-R1, UE-R2 according to the destinationaddresses, the group paths, and/or the like and may route the data tothe tunnel corresponding to UE-R1 and UE-R2 respectively.

In an example FIG. 18, a UE may establish a PDU session to join a group.After establishment of the PDU session, the UE may transition to idle(e.g., CM-IDLE). The UE may perform a service request procedure totransmit signaling, data, and/or the like. Upon successful completion ofthe service request procedure, the UE may transmit data packets for oneor more UEs of a group. The UPF may forward the data packets via N6interface, Nx interface or directly to the receiving UEs (e.g., localswitch).

In an example, as depicted in FIG. 23, a policy delivery procedure maybe employed. The policy delivery procedure may be employed to transmitthe URSP to the UE. In an example the PCF may determine to update UEpolicy procedures based on triggering conditions such as: an initialregistration, need for updating UE policy, and/or the like. In anexample, for initial registration case, the PCF may compare the list ofPSIs included in the UE access selection and PDU session selectionrelated policy information in a Npcf_UEPolicyControl_Create request andmay determine whether UE access selection and PDU session selectionrelated policy information have to be updated and be included in theresponse to the AMF. In an example, for the network triggered UE policyupdate case (e.g. the change of UE location, the change of SubscribedS-NSSAIs, activation of a group, and/or the like), the PCF may check thelatest list of PSIs to decide which UE access selection and/or PDUSession selection related policies have to be sent to the UE. The PCFmay check if the size of the resulting UE access selection and PDUSession selection related policy information exceeds a predefined limit.If the size is under the limit, then UE access selection and PDU Sessionselection related policy information may be included in a singleNamf_Communication_N1N2MessageTransfer service operation. If the sizeexceeds the predefined limit, the PCF may split the UE access selectionand PDU Session selection related policy information in smaller,logically independent UE access selection and PDU Session selectionrelated policy information ensuring the size of each is under thepredefined limit. One or more UE access selection and PDU Sessionselection related policy information may be sent in one or moreNamf_Communication_N1N2MessageTransfer service operations.

In an example, the PCF may invoke Namf_Communication_N1N2MessageTransferservice operation provided by the AMF. The message may comprise a SUPI,UE Policy Container, and/or the like. If the UE is registered andreachable by AMF in either 3GPP access or non-3GPP access, the AMF maytransfer transparently the UE policy container to the UE via theregistered and reachable access. If the UE is registered in both 3GPPand non-3GPP accesses and reachable on both access and served by thesame AMF, the AMF may transfer transparently the UE Policy container tothe UE via one of the accesses based on the AMF local policy. If the UEis not reachable by AMF over both 3GPP access and non-3GPP access, theAMF may report to the PCF that the UE Policy container may not bedelivered to the UE usingNamf_Communication_N1N2TransferFailureNotification. If AMFdetermines/decides to transfer transparently the UE Policy container tothe UE via 3GPP access, e.g. the UE is registered and reachable by AMFin 3GPP access only, or if the UE is registered and reachable by AMF inboth 3GPP and non-3GPP accesses served by the same AMF and the AMFdecides/determines to transfer transparently the UE Policy container tothe UE via 3GPP access based on local policy, and the UE is in CM-IDLEand reachable by AMF in 3GPP access, the AMF may start a pagingprocedure by sending a paging message to the UE. Upon reception ofpaging request, the UE may initiate the UE triggered service requestprocedure. If the UE is in CM-CONNECTED over 3GPP access or non-3GPPaccess, the AMF may send/transfer transparently the UE Policy container(e.g., UE access selection and PDU Session selection related policyinformation) received from the PCF to the UE. The UE Policy containermay comprise URSP, and/or the like. The UE may update the UE policyprovided by the PCF and may send the result to the AMF. If the AMFreceived the UE Policy container and the PCF subscribed to be notifiedof the reception of the UE Policy container, the AMF may forward theresponse of the UE to the PCF employing a Namf_N_1MessageNotify, and/orthe like. The PCF may maintain the list of PSIs delivered to the UE andmay update the latest list of PSIs in the UDR by invoking Nudr_DM_Update(e.g., comprising SUPI, Policy Data, Policy Set Entry, updated PSI data)service operation, and/or the like.

A 5GLAN Group may be managed (e.g., created, modified, and removed)based on AF request or UE request. A UE that belongs to the 5GLAN Groupmay access the 5G LAN-type service corresponding to the 5GLAN Group.

The UE may access the 5G LAN-type service by establishing a PDU session.During establishment of the PDU Session, the UE may beauthenticated/authorized for accessing the 5G LAN-type service. The 5GLAN-type service may support 5GLAN communication within the 5GLAN groupby coordinating PDU sessions of the UEs, e.g., traffic routing betweenPDU sessions may take place within the 5GS.

The 5GS may support the 5G LAN-type service by establishing a user planecomposed of one UPF or multiple interconnected UPFs. When the UEs withinthe 5GLAN group communicate with a physical LAN in the DN for one ormore data services, an Ethernet transport service may be associated withthe DN and may support connecting the UEs to the physical LAN in the DN.

The user plane of a 5G LAN-type service may comprise an access UP and abackbone UP. The access UP may comprise the UP path of a PDU Session, ofwhich UP paths terminates at an anchor UPF (e.g., not to a DN). Thebackbone UP may comprise one anchor UPF or multiple anchor UPFs with oneor multiple connections (e.g., Nx connections, tunnels, and/or the like)which may bridge the UP paths in the access UP with each other. The Nxconnections in the backbone UP may be managed by the 5GC. Trafficrouting over Nx in the backbone UP may be configured at the 5G LAN-typeservice level. The UPF(s) in the backbone UP may function as a router ora switch (Ethernet switch) and may treat the user plane path of the PDUsession as the cable connecting the UE to one port/interface on therouter or switch.

In an example, depending on implementation and operator's configuration,the backbone UP (e.g., comprising UPFs and Nx connections in between)may be pre-established before the UE requests PDU session for access tothe 5G LAN-type service and updated/modified afterward. The Nxconnections in the backbone UP may support IP traffic and/or Ethernettraffic and may be managed by the 5GC. An Nx connection may belong to aPDU session. The connection may be a per 5GLAN Group connection, sharedby multiple PDU Sessions for support of traffic routing between thoseSessions. Private communication (of 5G LAN-type service) is achieved byshared anchor UPF or by interconnecting two anchor UPFs via an Nxinterface. The combination of two anchor UPFs and the Nx interface inbetween may be an Nx connection. One or more Nx connections may befurther interconnected for the private communication in the same 5GLANgroup (e.g., depending how many group member UEs are involved).

An example FIG. 21 depicts an example of user plane topology for one tomany data communication. As depicted in FIG. 21, the group specific PDUSession may be terminated at the group member and the serving UPF. Whena group is established by one AF or one UE, a group specific PDU Sessionmay be established for each group member who are added into the groupwith the group creation. After the group creation, when a group memberis added into the group, the group specific PDU Session may beestablished for the new joined member. The SMF may be responsible forestablishing the forwarding tunnel between the UPF serving the newjoined member and the UPFs serving the authorized transmitting members.The PDU Session for UE-T, PDU Session for UE-R1, forwarding tunnel on N9interface for this group, PDU Session for UE-R2 compose the group dataforwarding path. UPF1 may forward the data received from UE-T to UE-R1and UPF2 according to group data forwarding path. If there are multipleUPFs (i.e. more than two UPFs) on the group data forwarding path, groupforwarding tunnel may be established on each N9 interface on the groupdata forwarding path. UPF(s) detect one to many communication based onthe destination address in the received data, e.g., if the destinationaddress in the received data is broadcast/multicast address, then theUPF(s) may forward the data to the related group members.

The access UP and the backbone UP may intersect at UPFs, which may bePSA UPFs from the access part point of view and BUAP (Backbone UP AccessPoint) UPFs from the backbone part point of view. Example FIG. 22depicts the user plane architecture of 5GLAN communication framework.

In an example, an authorized entity, e.g., a UE or an AF, may interactwith a GMF, UDM, UDR, NRF, and/or the like to manage a 5GLAN group. Thismay include to create, modify or remove a 5GLAN group, or to queryinformation related to a 5GLAN group, for example, information such asIP address of a member UE in the 5GLAN group. In an example, when a UEinteracts with the GMF, UDM, UDR, NRF, and/or the like, the UE may senda request for 5GLAN group management to the GMF, UDM, UDR, NRF, and/orthe like, via the AMF, and the UE request may be authorized by the GMFaccording to subscription information, e.g. whether the UE is authorizedto create a 5GLAN group. In an example, when an AF interacts with theGMF, the AF may send a request for 5GLAN group management to the GMFdirectly or via the NEF, depending on whether operator allows the AF toaccess the network directly. When the NEF is involved, the NEF mayauthorize the AF request if the AF request is not yet authorized. Therequest may comprise GPSI if the requesting entity is a UE, orAF-service-ID if the requesting entity is an AF, and 5G LAN-VN DNN.Depending on the management purpose, the request may further comprisetype of traffic (e.g. IP type or Ethernet type) to be supported during5GLAN communication, metadata of the 5GLAN group (e.g. describing thepurpose of the 5GLAN group), identity information (e.g. GPSIs of the UEsto be added in or removed from the 5GLAN group), service restrictions(e.g., allowed area), information identifying the 5GLAN group (e.g., inthe form of Internal group ID or External group ID), the types ofinformation (e.g., information of member UEs) being queried, and/or thelike. The GMF may validate the information provided by the entity, e.g.,whether a member UE identified in the information is allowed to accessthe 5G LAN-type service, and manages the 5GLAN group according to theinformation. As a result of the 5GLAN group management operations, thecontext of the 5GLAN group is created, modified, or removed in the GMF,UDM, UDR, and/or the like or information being queried by the entity isidentified from local storage of the GMF, UDM, UDR, and/or the like andsent back to the requesting entity. The GMF may update the 5GLAN groupmembership information to the UDM. The GMF may provide policyrequirements (e.g., service restrictions) to the PCF. When creating a5GLAN group, the GMF may allocate an ID to the 5GLAN group and mayinclude the 5GLAN group ID in the response sent to the requestingentity. When a UE is added into the 5GLAN group, the GMF may allocategroup credential for the UE, which is to be provided by the UE to thenetwork as authentication and authorization information for accessing 5GLAN-type service for the 5GLAN group.

In an example, the wireless communication system, e.g., the 3GPP system,5GS, 4G, LTE, and/or the like may be employed for group communication,UE to UE communication session, one UE to/from one or more UE(s)communication session(s), one to many communication, and/or the like.

An example FIG. 24 depicts one or more UEs that may perform a PDUsession establishment to join a group. The SMF allocates or retrievesthe multicast information associated with the group and provide themulticast information to the UE members of the group. The SMF mayprovide the PDR, packet handling rules, and FAR to the UPF based on themulticast information.

FIG. 27 depicts an example legacy system signaling when data packets fora group of UEs is received by the UPF. A UPF may receive data for alarge group of wireless devices. In legacy systems, if the CNtunnel/user plane connection is not activated, data notificationmessages may be sent to the SMF. The number of data notificationmessages may correspond to the number of (inactive) wireless devices inthe group. If there is a large number of inactive wireless devices,excessive reliance on data notification messages may cause signalingoverload in the core network, leading to an inefficient utilization ofresources. To address this problem, the present application employs newtechniques for activating wireless devices while reducing the signalingload in the network.

For example, the UPF instead of sending a large number of datanotification messages, may employ a different mechanism to signal thearrival of data packets for the group. The UPF is configured with amulticast address corresponding to the group, it may use the multicastaddress to reduce signaling. By sending a single data notificationmessage comprising the multicast address to the SMF, the signalingoverhead/overload for a large group may be mitigated.

If the SMF is configured with an association between the multicastaddress and the group of wireless devices in the group, it may employthe group information to assist the AMF to identify and activate theinactive wireless devices in the group. Just as signaling overload isreduced when using a multicast address for communication between the UPFand the SMF, group information may be employed to achieve similarreduction in signaling overhead when communicating between the SMF andthe AMF. If the AMF is configured with the association between the groupinformation and the wireless devices in the group, the AMF can identifyand activate the inactive wireless devices of the group.

In an example embodiment as described in the present application, a UPFmay receive data packets targeted to a group of UEs. The sender may be atransmitting wireless device, an application, an application server, andapplication function, and/or the like. When the UPF determines that thedestination address is a multicast, and the data packet is targeted to agroup of UEs, the UPF may send a single data notification to activatethe UEs in the group. The single data notification may provide to theSMF multicast information, multicast address, and/or the like todetermine the group of wireless devices, and the PDU sessions associatedwith the wireless devices of the group. The SMF may provide the groupinformation or group identifier to the AMF. The group may be identifiedby a combination or one or more of a DNN, a S-NSSAI, a group ID,internal/external group id, and/or the like. The AMF may determine theUE members are determine an action based on the status of the UE such asreachability, connectivity, IDLE, CONNECTED, INACTIVE, and/or the like.The AMF may determine to notify the UEs via a base station, RAN, NG-RAN,wireless access point, and/or the like. The UEs upon receiving thenotification may respond by performing a service request with thenetwork.

An example FIG. 25 depicts a UPF that is configured based on themulticast information, and receives data for the group associated withthe multicast information. The UPF may send a data notification that maycomprise multicast information, multicast address, a PDR ID associatedwith the group, and/or the like to the SMF. The SMF may determine agroup information and notify the AMF to activate the group. The AMF mayactivate the UE members of the group that may require user planeconnection/resources activation.

In an example embodiment, a VN group, a 5GLAN group communication,and/or the like may comprise communication among one or more wirelessdevices. The group communication may comprise multicast. The groupcommunication may comprise anycast. The group communication may comprisegeocast. The group communication may comprise broadcast. The groupcommunication may comprise group communication/routing/switching. Themulticast information may refer to an address. The multicast informationmay refer to an identity. The multicast information may refer to adetermination/identification of the group communication. In an example,the multicast information may be a multicast address. The multicastinformation may be a multicast IP address. The multicast information maybe a multicast MAC address. The multicast information may comprise anidentifier of a receiving wireless device. The multicast information maycomprise an identifier/identifiers/addresses of one or more wirelessdevices. The multicast information may comprise a subset of wirelessdevices of a group. In an example, the group may comprise one or morewireless devices. In an example, the group may comprise a group ofwireless devices reachable via a domain. The group may comprise a groupof wireless devices reachable via an IP domain. The group may comprise agroup of wireless devices reachable via a multicast address. The groupmay comprise a group of wireless devices reachable via a networkinstance. The group may comprise a group of wireless devices reachablevia a VLAN. The group may comprise a group of wireless devices reachablevia a VLAN ID. The group may comprise a group of wireless devicesreachable via an S-TAG. The group may comprise a group of wirelessdevices reachable via a C-TAG. The group may comprise a group ofwireless devices reachable via a VLAN TAG. The group may comprise agroup of wireless devices reachable via a group GTP tunnel identifier.The group may comprise a group of wireless devices reachable via a groupGTP tunnel end point identifier. In an example, the network instance maybe employed to separate IP domains. An IP domain may comprise aninstance where UPF is connected to 5G-ANs in different IP domainsoverlapping UE IP addresses assigned by multiple Data Networks, and fortransport network isolation in the same PLMN, and/or the like.

In an example embodiment, multicast information may comprise one or moremulticast addresses. Multicast information may comprise a tunnelidentifier of the group. Multicast information may comprise an AN tunnel(identifier) for the group. Multicast information may comprise one ormore tunnel identifiers associated with members of the group. Multicastinformation may comprise a set of one or more UE members of the group.Multicast information may comprise an identifier of a UE member of thegroup (UE ID, SUPI, and/or the like). Multicast information may comprisean identifier/address of a UE acting as a VLAN switch/router and a portnumber that connects a VLAN group associated with the group to thenetwork via the UE-T, a VLAN ID, V-TAG, C-TAG, S-TAG, VLAN TAG, and/orthe like.

In an example embodiment, data notification may part of an N4 relatedprocedure, PFCP session related procedure, N4 reporting to detection ofarrival of packets, N4 reporting for detection of inactivity for PDUsessions of a group, and/or the like.

In an example embodiment the PDU session establishment procedure asdepicted in FIG. 12 and FIG. 13, and FIG. 20 may be employed by awireless device to join a virtual network VN group communication. In anexample, when the UE sends to the AMF the NAS Message (or the SM NASmessage), if the UE is establishing the PDU session for sending one tomany communication data of a 5GLAN group, VN group, and/or the like itmay indicate that it requests a multicast address, multicastinformation, and/or the like. The UE may indicate the group informationwithin the N1 SM container. If the UE is establishing the PDU sessionfor receiving one to many communication data of a 5GLAN group, it mayindicate the group information and may indicate that it is a receiver ofthe group within the N1 SM container.

In an example embodiment, when the AMF receives the NAS message, if therequest type indicates initial request and the UE subscription indicatesthe support for 5G LAN-type (e.g., VN group, and/or the like) servicefor the requested DNN, the AMF may select the SMF associated with therequested DNN in UE subscription data received from a UDM. The casewhere the request type indicating initial request and the UEsubscription indicating the support for 5G LAN-type service for therequested DNN, and UE subscription received from the UDM during theregistration or subscription profile update notification procedure doesnot contain SMF information corresponding to the requested DNN mayconstitute an error case, the AMF may reject the NAS message containingPDU Session Establishment Request from the UE with a cause indicatingthat the requested 5G LAN-type service is not supported.

In an example, when the SMF receives the PDU session establishmentrequest if the request indicates the one to many communication, VNgroup, group communication, and/or the like establishment request for anindicated group, the SMF may allocate a 5GLAN group (VN group) uniquemulticast address (e.g., IP address for IP type PDU session, MAC addressfor Ethernet type, and/or the like). In an example, the SMF may obtainthe address information for the one to many communication from 5GLANgroup provision information (e.g., from a UDR, UDM, PCF, a repositoryfunction, a group management function, locally configured information,and/or the like).

In an example, during the PDU session establishment procedure, the SMFmay perform the N4 session establishment or N4 session modificationprocedure. The SMF may sends the N4 session establishment/modificationrequest to the UPF and may provide packet detection (e.g., PDR),forwarding (e.g., FAR), enforcement and reporting rules to be installedon the UPF for the PDU session. If CN tunnel info is allocated by theSMF, the CN Tunnel Info may be provided to the UPF. If selective userplane deactivation is required for the PDU Session, the SMF maydetermine the inactivity timer and may provide it to the UPF. The SMFmay provide trace requirements to the UPF if it has received tracerequirements. If the PDU Session is targeting to the DNN associated witha 5GLAN group, the SMF may create the packet detection and forwardingrules in order to bind the session or service data flow to the related5G LAN-VN. The packets detection include session tunnel information, UEaddress, and/or the like and the packets forwarding rules may includethe related VLAN ID, 5G LAN-VN ID, and/or the like. In an example, whenthe PDU session is for sending and/or receiving one to manycommunication data of a 5GLAN group, the SMF may provide the multicastaddress, multicast information, and/or the like to the UPF for detectingpackets, and receiving packets from the PDU session or sending packetsto the PDU session.

In an example, when the PDU session establishment is in progress, theSMF may send to the AMF the Namf_Communication_N1N2MessageTransfermessage that may comprise the PDU Session ID, N2 SM information (PDUSession ID, QFI(s), QoS Profile(s), CN Tunnel Info, S-NSSAI from theAllowed NSSAI, Session-AMBR, PDU Session Type, User Plane SecurityEnforcement information, UE Integrity Protection Maximum Data Rate), N1SM container (PDU Session Establishment Accept (QoS Rule(s) and QoS Flowlevel QoS parameters if needed for the QoS Flow(s) associated with theQoS rule(s), selected SSC mode, S-NSSAI(s), DNN, allocated IPv4 address,interface identifier, Session-AMBR, selected PDU Session Type,Reflective QoS Timer (if available), P-CSCF address(es), [Always-on PDUSession], allocated multicast address, the multicast address for one tomany communication, the multicast information, and/or the like))). Ifmultiple UPFs are employed for the PDU Session, the CN Tunnel Info maycontain tunnel information related with the UPF that terminates N3.

In an example, during the PDU session establishment procedure, the UPFmay provide the N4 session modification response to the SMF. If multipleUPFs are employed in the PDU Session, the UPF may be the UPF terminatingN3. If the PDU Session is targeting to the DNN associated with the 5GLANgroup, the SMF may create new packet handling rules (PHRs) including theUE address and the association to the downlink packet forwarding rulesof the PDU Session. The SMF may initiate N4 PHRs management procedure toupdate the PHRs for the corresponding 5G LAN-VN group in the UPF.

In an example, during the PDU session establishment procedure, the AMFmay send to the (R)AN the N2 PDU Session Request (N2 SM information, NASmessage (PDU Session ID, N1 SM container (PDU Session EstablishmentAccept))). In an example, the N2 PDU Session Request, the N2 SMinformation, the NAS message, and/or the like may comprise the multicastaddress, multicast information, and/or the like of the 5GLAN group (VNgroup). The AMF may send the NAS message containing PDU Session ID andPDU Session Establishment Accept targeted to the UE and the N2 SMinformation received from the SMF within the N2 PDU Session Request tothe (R)AN. The (R)AN may issue to the UE the AN specific signallingexchange with the UE that is related with the information received fromSMF. For example, in case of a NG-RAN, an RRC Connection Reconfigurationmay take place with the UE establishing the necessary NG-RAN resourcesrelated to the QoS Rules for the PDU Session request. The AN specificsignalling exchange procedure may be employed to transmit the multicastinformation, multicast address and/or the like to the UE. The (R)AN mayallocate (R)AN N3 tunnel Info for the PDU Session. The (R)AN mayforwards the NAS message (multicast address, multicast information, thePDU Session ID, N1 SM container (PDU Session Establishment Accept)) tothe UE.

In an example embodiment, upon successful establishment of the PDUsession, the UPF may transmit the multicast information, multicastaddress, and/or the like associated with the 5GLAN, VN group, to the UEvia a user plane connection. An advertising mechanism may be employed totransmit/deliver/send the multicast information of the group to the UE.

In an example embodiment, a network triggered service request proceduremay be performed. The network triggered service request procedure may beemployed when the network determined/needs to signal (e.g., N1signalling to UE, Mobile-terminated SMS, User Plane connectionactivation for PDU Session(s) to deliver mobile terminating user data)with a UE. When the procedure is triggered by SMSF, PCF, LMF, GMLC, NEFor UDM, the SMF may be replaced by the respective NF. If the UE is in CMIDLE state or CM-CONNECTED state in 3GPP access, the network mayinitiate a Network Triggered Service Request procedure. If the UE is inCM-IDLE state, and asynchronous type communication is not activated, thenetwork may send a paging request to (R)AN/UE. The paging request maytrigger the UE triggered service request procedure (as depicted in FIG.10 and FIG. 11) in the UE. If asynchronous type communication isactivated, the network may store the received message and forward themessage to the (R)AN and/or the UE (e.g., may synchronize the contextwith the (R)AN and/or the UE) when the UE enters CM-CONNECTED state. Ifthe UE is in CM-IDLE state in non-3GPP access and if the UE issimultaneously registered over 3GPP and non-3GPP accesses in a PLMN, thenetwork may initiate a network triggered service request procedure over3GPP access. If the UE is in CM-IDLE state in 3GPP access and inCM-CONNECTED state in non-3GPP access, and if the UE is simultaneouslyregistered over 3GPP and non-3GPP accesses in the same PLMN, the networkmay initiate a Network Triggered Service Request procedure for 3GPPaccess via non-3GPP access.

In an example embodiment as depicted in FIG. 28 and FIG. 29, a UPF mayreceive downlink data, data packets, and/or the like for a PDU Session,one or more PDU sessions associated with a multicast address, multicastinformation, a group, and/or the like. In an example, the UPF mayreceive the data packets from a transmitting wireless device that may bea member of VN group for a UE to UE communication, one to manycommunication, and/or the like. The UPF may determine that the datapackets are for the VN group based on packet filters configured at theUPF. The UPF may determine that the data packets may be targeted to agroup of receiving wireless devices. The UPF may determine that themulticast information may be employed to transmit the data packets tothe group. The UPF may determine that data packets may be sent to adestination address that may be the multicast address. The UPF maydetermine that there is no AN Tunnel Info stored in UPF for the PDUSession, the one or more PDU sessions associated with a multicastaddress, multicast information, a group, and/or the like. The UPF basedon the instruction from the SMF may buffer the downlink data, or forwardthe downlink data to the SMF. The UPF may receive the data packets froman intermediate UPF via an Nx interface. The intermediate UPF may servethe transmitting wireless device, one or more receiving wirelessdevices, or wireless devices associated with the group.

In an example, when the UPF determines that user plane connection forthe group, or one or more UE member of the group is not activated, theUPF may send a data notification message to the SMF. In an example, thedata notification message may comprise the multicast information. In anexample, the data notification message may comprise the multicastaddress. In an example, the data notification message may comprise a PDRrule id, PDR ID, and/or the like associated with the packet detectionrule for the group. In an example, the data notification message maycomprise a network instance, an N4 session ID, and/or the like. In anexample, the data notification message may comprise an N4 session IDassociated with one of the sessions (PDU sessions) associated with thegroup, a UPF identifier, UPF address, and/or the like. In an example,the data notification message may comprise one or more N4 Session IDsassociated with the multicast information or the group, information toidentify the QoS Flow for the DL data packets, DSCP, and/or the like. Inan example, upon arrival of the first downlink data packet for any QoSFlow, the UPF may send the data notification message to the SMF, if theSMF has not previously notified the UPF to not send the datanotification to the SMF. If the UPF receives downlink data packets foranother QoS Flow in the same PDU Session, the UPF may send another datanotification message to the SMF. In an example, if paging policydifferentiation feature is supported by the UPF and if the PDU Sessiontype is IP, the UPF may include the DSCP in TOS (IPv4)/TC (IPv6) valuefrom the IP header of the downlink data packet and the information toidentify the QoS Flow for the DL data packet. In an example, the SMF maysend to the UPF a data notification acknowledgment message.

In an example, the UPF may forward the (downlink) data packets towardsthe SMF if the SMF instructed the UPF and the SMF may buffer the datapackets. If the Paging Policy Differentiation feature is supported bythe SMF and if the PDU Session type is IP, the SMF may determine thepaging policy indicator based on the DSCP in TOS (IPv4)/TC (IPv6) valuefrom the IP header of the received downlink data packet and may identifythe corresponding QoS Flow from the QFI of the received DL data packet.

In an example, the SMF may identify a corresponding group based on oneor more elements of the data notification message.

In an example embodiment, when the SMF receives the data notificationcomprising the multicast information, multicast address, and/or thelike, the SMF may map the multicast information or the multicast addressto a group information, group identifier, and/or the like. In anexample, the SMF may determine group information, group identifierassociated with a group of wireless device based on the multicastinformation or the multicast address, and/or the like.

In an example, a UPF may be dedicated to the group. In an example, whenthe SMF receives data notification comprises the UPF identifier, UPFaddress and the N4 session ID, the SMF may identify the group anddetermine the group information, group identifier, and/or the like basedon one or more elements of the data notification message.

In an example, the SMF may send to the AMF, an N11 message, e.g.,Namf_Communication_N1N2MessageTransfer. The N11 message may comprise aSUPI, one or more PDU Session ID, N1 SM container (SM message), N2 SMinformation (QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI), Areaof validity for N2 SM information, ARP, Paging Policy Indicator, 5QI,N1N2TransferFailure Notification Target Address), or NF to AMF:Namf_Communication_N1N2MessageTransfer (SUPI, N1 message), and/or thelike. In an example, the N11 message (e.g.,Namf_Communication_N1N2MessageTransfer) may comprise the groupinformation, the group identifier, identifiers of one or more wirelessdevices, a subset of group of wireless devices, and/or the like.

The SMF may determine whether to contact the AMF. The determining may bebased on whether the SMF had previously been notified that the UE isunreachable, whether the UE is reachable only for regulatory prioritizedservice and the PDU Session is not for regulatory prioritized service,and/or the like.

In an example, the SMF may determine the AMF and may invokes theNamf_Communication_N1N2MessageTransfer to the AMF including themulticast information, group information, group identifier, multicastaddress, and/or the like. In an example, theNamf_Communication_N1N2MessageTransfer may comprise the PDU Session IDsof the one or more PDU Sessions. In an example, the SMF may determinethe PDU Session ID based on the N4 Session ID.

In an example, if the SMF, while waiting for the user plane connectionto be activated, receives any additional data notification message or,in the case that the SMF buffers the data packets, additional datapackets for a QoS Flow associated with a higher priority (i.e. ARPpriority level) than the priority indicated to the AMF in the previousNamf_Communication_N1N2MessageTransfer, or the SMF derive a differentPaging Policy Indicator according to the additional Data Notification orthe DSCP of the data packet, the SMF may invoke a newNamf_Communication_N1N2MessageTransfer indicating the higher priority ordifferent Paging Policy Indicator to the AMF. In an example, if the SMF,while waiting for the user plane to be activated, receives a messagefrom a new AMF other than the one to which the SMF invokedtheNamf_Communication_N1N2MessageTransfer, the SMF may re-invoke theNamf_Communication_N1N2MessageTransfer towards the new AMF.

In an example, when supporting paging policy differentiation, the SMFmay determine the paging policy indicator related to the groupinformation, the group, the multicast information, and/or the like. Thepaging policy indicator may be determined based on downlink data thathas been received from the UPF or triggered the data notificationmessage, based on the DSCP. The SMF may indicate the paging policyindicator in the Namf_Communication_N1N2MessageTransfer.

In an example, the AMF may respond to the SMF. If the UE is in CM-IDLEstate at the AMF, and the AMF is able to page the UE the AMF may send aNamf_Communication_N1N2MessageTransfer response to the SMF with a causeindicating attempting to reach UE which may indicate to the SMF that theN2 SM information, may be ignored by the AMF once the UE is reachableand the SMF may be asked to provide the N2 SM information again. In anexample, while waiting for the UE to respond to a previous pagingrequest, if the AMF receives an Namf_Communication_N1N2MessageTransferRequest message with the same or a lower priority than the previousmessage triggering the paging, or if the AMF has determined not totrigger additional paging requests for the UE based on local policy, theAMF may reject the Namf_Communication_N1N2MessageTransfer Requestmessage. If the UE is in CM-CONNECTED state at the AMF then the AMF maysend a Namf_Communication_N1N2MessageTransfer response to the SMF with acause value indicating that N1/N2 transfer is successful. If the UE isin CM-IDLE state, and the AMF determines that the UE is not reachablefor paging, the AMF may send an Namf_Communication_N1N2MessageTransferresponse to the NF (e.g., SMF) from which AMF received the requestmessage. In an example, the AMF may perform asynchronous typecommunication and may store the UE context based on the receivedmessage. If asynchronous type communication is invoked, the AMF mayinitiate communication with the UE and the (R)AN node when the UE isreachable e.g., when the UE enters CM-CONNECTED state. If the AMF hasdetermined the UE is unreachable for the SMF (e.g., due to the UE inMICO mode or the UE is only registered over non-3GPP access and itsstate is CM-IDLE), then the AMF may reject the request from the SMF. TheAMF may include in the reject message an indication that the SMF neednot trigger the Namf_Communication_N1N2MessageTransfer Request to theAMF, if the SMF has not subscribed to the event of the UE reachability.The AMF may store an indication that the SMF has been informed that theUE is unreachable. If the UE is not in MICO mode and the AMF detects theUE is in a Non-Allowed Area unless the request from the SMF is forregulatory prioritized service, the AMF may reject the request from theSMF and may notify the SMF that the UE is reachable only for regulatoryprioritized service. The AMF may store an indication that the SMF hasbeen informed that the UE is reachable only for regulatory prioritizedservice. If the Registration procedure with AMF change is in progresswhen the old AMF receives the Namf_Communication_N1N2MessageTransfer,the old AMF may reject the request with an indication that theNamf_Communication_N1N2MessageTransfer has been temporarily rejected.Upon reception of an Namf_Communication_N1N2MessageTransfer responsewith an indication that its request has been temporarily rejected, theSMF may start a locally configured guard timer and wait for any messageto come from an AMF. Upon reception of a message from an AMF, the SMFmay re-invoke the Namf_Communication_N1N2MessageTransfer (with N2 SMinfo and/or N1 SM info) to the AMF from which it received the message.If the SMF determines/decides that the control plane buffering applies,the SMF may request UPF to start forwarding the downlink data PDUtowards the SMF.

In an example, the SMF may respond to the UPF. The SMF may notify theUPF about the User Plane setup failure. If the SMF receives anindication from the AMF that the UE is unreachable or reachable only forregulatory prioritized service, the SMF may, based on network policies,either indicate to the UPF to stop sending Data Notifications, indicateto the UPF to stop buffering DL data and discard the buffered data,indicate to the UPF to stop sending Data Notifications and stopbuffering DL data and discard the buffered data, or may refrain fromsending further Namf_Communication_N1N2MessageTransfer message for DLdata to the AMF while the UE is unreachable. Based on operator policies,the SMF may apply the pause of charging procedure. If the SMF receivesan indication from the AMF that theNamf_Communication_N1N2MessageTransfer message requested from an SMF hasbeen temporarily rejected, the SMF may, based on network policies,indicate to the UPF to apply temporary buffering.

According to an example embodiment, in response to receiving the N11message from the SMF, the AMF may determine that one or more wirelessdevices associated with the group may in idle state CM-IDLE, requireuser plane activation, and/or the like. The determining, by the AMF, maybe based on: the group information, multicast information, and/or thelike. In an example, the AMF may determine the members of the groupassociated with the multicast information, PDU session IDs (associatedwith the VN group—receiving wireless devices) received from the SMF, orobtain the group information associated with the multicast informationfrom a repository e.g., UDM/UDR, a group management function, a policyfunction, and/or the like. The AMF may determine from a list/set of UEsassociated with the group or associated with the PDU session IDsreceived from the SMF, one or more UEs (wireless devices) that are inidle state and may send one or more paging messages to the one or moreUEs in idle state. In an example, the AMF may determine to activate theuser plane connection of the UEs that are associated with the group.

In an example embodiment, the AMF upon reception of the N11 messagecomprising the group information, may determine to activate one or morereceiving wireless devices of the group. The AMF may perform pagingprocedure to page the receiving wireless devices of the group. Thereceiving wireless devices in response to the paging message may performthe UE triggered service procedure as depicted in FIG. 10 and FIG. 11.Upon completion of the service request procedure for the UEs, the UPFmay forward the data packets (received from UE-T) to the group.

In an example, if a UE is in CM-CONNECTED state in the access associatedwith the PDU Session ID received from the SMF the UE Triggered ServiceRequest procedure may be performed for the PDU Session (e.g., establishthe radio resources and, in the case that the User Plane is to beactivated, to establish the N3 tunnel) without sending a paging messageto the (R)AN node and the UE. In an example, if the UE is in CM-IDLEstate in 3GPP access and the PDU Session ID received from the SMF hasbeen associated with 3GPP access and based on local policy the AMFdecides to notify the UE through 3GPP access even when UE is inCM-CONNECTED state for non-3GPP access, the AMF may send a pagingmessage to NG-RAN node(s) via 3GPP access. If the UE is simultaneouslyregistered over 3GPP and non-3GPP accesses in the same PLMN, the UE isin CM-IDLE state in both 3GPP access and non-3GPP access, and the PDUSession ID is associated with non-3GPP access, the AMF may send a pagingmessage with associated access “non-3GPP” to NG-RAN node(s) via 3GPPaccess. If the UE is in RM-REGISTERED state and CM-IDLE and reachable in3GPP access, the AMF may send a paging message (e.g., comprising NAS IDfor paging, Registration Area list, Paging DRX length, Paging Priority,access associated to the PDU Session, Enhanced Coverage Restrictedinformation) to (R)AN node(s) belonging to the Registration Area(s) inwhich the UE is registered, then the NG-RAN node may page the UE,including the access associated to the PDU Session in the paging messageif received from the AMF. If extended idle mode DRX was accepted by theAMF in the last registration procedure, the AMF may include extendedidle mode DRX cycle length and paging time window in the paging message.

In an example, the AMF may be configured with different pagingstrategies based on the group information, multicast information, and/orthe like. The AMF may be configured with different paging strategiesbased on different combinations of DNN, Paging Policy Indicator (ifsupported), ARP and 5QI, and/or the like. For RRC-inactive state, thepaging strategies may be configured in the (R)AN for differentcombinations of group information, multicast information, paging policyindicator, ARP and 5QI, and/or the like. Paging Priority may be includedwhen the AMF receives an Namf_Communication_N1N2MessageTransfer messagewith an ARP value associated with priority services (e.g., MPS, MCS), asconfigured by the operator. Paging Priority may be included when onepaging priority level can be used for multiple ARP values. The mappingof ARP values to paging priority level (or levels) may be configured byoperator policy in the AMF and in NG-RAN.

In an example, the (R)AN may prioritize the paging of UEs according tothe paging priority. Paging priority may be based on the groupinformation, multicast information, and/or the like. If the AMF, whilewaiting for a UE response to the paging request message sent withoutpaging priority, receives an Namf_Communication_N1N2MessageTransfermessage, which indicates an ARP value associated with priority services(e.g., MPS, MCS), as configured by the operator, the AMF may sendanother paging message with the suitable paging priority. For subsequentreceived Namf_Communication_N1N2MessageTransfer messages with the sameor higher priority, the AMF may determine whether to send the pagingmessage with suitable paging priority based on local policy. In anexample, paging strategies may comprise: paging retransmission scheme(e.g., how frequently the paging is repeated or with what timeinterval), determining whether to send the Paging message to the (R)ANnodes during certain AMF high load conditions, whether to apply sub-areabased paging (e.g. first page in the last known cell-id or TA andretransmission in all registered TAs), and/or the like.

In an example, the AMF and/or the (R)AN may support further pagingoptimizations in order to reduce the signalling load and the networkresources used to successfully page a UE. The paging optimizations maycomprise implementing by the AMF specific paging strategies (e.g., theN2 Paging message is sent to the (R)AN nodes that served the UE last),considering by the AMF information on recommended cells and NG-RAN nodesprovided by the (R)AN at transition to CM-IDLE state, and/or the like.The AMF may take the (R)AN nodes related part of this information intoaccount to determine the (R)AN nodes to be paged, and provides theinformation on recommended cells within the N2 Paging message to each ofthese (R)AN nodes. Paging optimizations may further comprise consideringby the (R) The paging attempt count information provided by the AMF atpaging. If the UE radio capability for paging information is availablein the AMF, the AMF may add the UE radio capability for paginginformation in the N2 paging message to the (R)AN nodes. If theinformation on recommended cells and (R)AN nodes for paging is availablein the AMF, the AMF may take that information into account to determinethe (R)AN nodes for paging and, when paging a (R)AN node, the AMF maytransparently convey the information on recommended cells to the (R)ANnode. The AMF may include in the N2 paging message(s) the paging attemptcount information. The paging attempt count information may be the samefor all (R)AN nodes selected by the AMF for paging.

In an example, if the UE is simultaneously registered over 3GPP andnon-3GPP accesses in the same PLMN, and the UE is in CM-CONNECTED statein 3GPP access and the PDU Session ID is associated with non-3GPPaccess, the AMF may send a NAS notification message containing thenon-3GPP access type to the UE over 3GPP access and sets a notificationtimer. If the UE is simultaneously registered over 3GPP and non-3GPPaccesses in the same PLMN, and the UE is in CM-CONNECTED state fornon-3GPP access and in CM-IDLE for 3GPP access, and if the PDU SessionID is associated with 3GPP access, and based on local policy the AMFdecides/determines to notify the UE through non-3GPP access, the AMF maysend a NAS notification message containing the 3GPP access type to theUE over non-3GPP access and sets a notification timer.

In an example, the AMF may send to the SMF anNamf_Communication_N1N2Transfer Failure Notification. The AMF maysupervise the paging procedure with a timer. If the AMF receives noresponse from the UE to the paging request message, the AMF may applyfurther paging according to any applicable paging strategy. The AMF maynotify the SMF by sending Namf_Communications_N1N2MessageTransferFailure Notification to the notification target address provided by theSMF, if the UE does not respond to paging, unless the AMF is aware of anongoing MM procedure that prevents the UE from responding, e.g., the AMFreceives an N14 Context Request message indicating that the UE performsRegistration procedure with another AMF. When aNamf_Communication_N1N2Transfer Failure Notification is received, theSMF may inform the UPF and procedure for pause of charging at SMF may beperformed.

In an example, if the UE is in CM-IDLE state in 3GPP access, uponreception of paging request for a PDU session associated to 3GPP access,the UE may initiate the UE triggered service request procedure. The AMFmay invoke Nsmf_PDUSession_UpdateSMContext request to the SMF(s)associated with the PDU session identified in service request message.To support the buffered data forwarding, the SMF may instruct the UPF toestablish a data forwarding tunnel between the old UPF and the new UPFor to the PSA. If the UE is in CM-IDLE state in both non-3GPP and 3GPPaccesses, upon reception of paging request for a PDU Session associatedto non-3GPP access, the UE may initiate the UE triggered service requestprocedure which may comprise the list of allowed PDU sessions that,according to UE policies and whether the S-NSSAIs of these PDU Sessionsare within the Allowed NSSAI for 3GPP access, can be re-activated overthe 3GPP access. If there is no PDU session that can be re-activatedover the 3GPP access, the UE may include an empty List Of Allowed PDUSessions. If the AMF receives a service request message from the UE vianon-3GPP access (e.g., because the UE successfully connects to anon-3GPP access), the AMF may stop the paging procedure and may processthe received service request procedure. If the AMF receives the servicerequest message and the list of allowed PDU Sessions provided by the UEdoes not include the PDU Session for which the UE was paged, the AMF maynotify the SMF that the UE was reachable but did not accept tore-activate the PDU session by invoking a Namf_EventExposure_Notifyservice.

In an example, if the UE is in CM-IDLE state in non-3GPP access and inCM-CONNECTED state in 3GPP access, upon reception of NAS Notificationmessage over 3GPP access containing the non-3GPP Access Type, the UE mayinitiate the UE triggered service request procedure with the list ofallowed PDU sessions that, according to UE policies and whether theS-NSSAIs of these PDU Sessions are within the Allowed NSSAI for 3GPPaccess, can be re-activated over the 3GPP access. If there is no PDUsession that can be re-activated over the 3GPP access, the UE mayinclude an empty list of allowed PDU sessions. When the AMF receives theservice request message and the list of allowed PDU sessions provided bythe UE does not include the PDU session for which the UE was notified,the AMF may notify the SMF that the UE was reachable but did not acceptto re-activate the PDU Session by invoking Namf_EventExposure_Notifyservice. If the AMF receives a service request message from the UE vianon-3GPP access (e.g., because the UE successfully connects to anon-3GPP access), the AMF may stop the notification timer and processesthe received service request procedure.

In an example, if the UE is in CM-IDLE state in 3GPP access and inCM-CONNECTED state in non-3GPP access, upon reception of NASnotification message over non-3GPP access identifying the 3GPP accesstype, the UE may initiate the UE triggered service request procedureover the 3GPP access when 3GPP access is available. If the AMF does notreceive the service request message before notification timer expires,the AMF may either page the UE through 3GPP access or notify the SMFthat the UE was not able to re-activate the PDU session.

In an example, the UPF may transmit the buffered downlink data towardsthe UEs via (R)AN node(s) which performed the service request procedure.The network may send downlink signalling to the UE if the procedure istriggered due to request from other NFs.

In an example embodiment, a selective deactivation of UP connection forPDU sessions of a group may be employed. The procedure may be employedto deactivate UP connection (e.g., data radio bearer and/or N3 tunnel)for an established PDU Session of a UE in CM-CONNECTED state.

In an example, when an inactivity timer for a PDU session is provided bySMF during N4 Session Establishment/Modification procedure, and the UPFmay detect that one or more PDU session have no data transfer for aperiod specified by the Inactivity Timer, it may report PDU SessionInactivity to the SMF. The report of PDU session inactivity maycorrespond to one or more PDU sessions of a group of wireless devicesthat may receive data packets based on the multicast information,multicast address, and/or the like. An N4 session report may be employedto report inactivity for a group of UEs. The N4 session report maycomprise an N4 Session ID, a list of [Reporting trigger, Measurementinformation], and/or the like. The N4 session report may comprise themulticast information, the multicast address, and/or the like.

The SMF may determine the corresponding group based on one or moreelements of the N4 session report. In an example, the SMF may determinethat the UP connection of one or more PDU session(s) associated with thegroup may be deactivated. The determining may be based on the UPFdetecting that the one or more PDU session(s) have no data transfer fora specified Inactivity period. The SMF may determine/decide to releasethe UPF of N3 terminating point. The SMF may initiate an N4 SessionRelease procedure to release the intermediate UPF of N3 terminatingpoint. If there are multiple intermediate UPFs, this step can beperformed for each UPFs to be released. The SMF may need to initiate N4Session Modification procedure to the UPF (e.g., N9 terminating point orPDU Session Anchor) connecting to the released UPF. If the intermediateUPF(s) of N3 terminating point is released, the SMF may initiate an N4session modification procedure towards the UPF (PDU Session Anchor oranother intermediate UPF) connecting to the released UPF, indicating theneed to remove AN Tunnel Info for N3 tunnel of the corresponding PDUSession. The UPF connecting to the released UPF may buffer the DLpackets for the one or more PDU Session(s) or drop the DL packets forthe PDU session or forward the DL packets for the one or more PDUsession(s) to the SMF, based on buffering instruction provided by theSMF.

In an example, if the UPF of N3 terminating point is not released, theSMF may initiates an N4 session modification procedure indicating theneed to remove AN Tunnel Info for N3 tunnel of the corresponding to theone or more PDU Session(s). In this case, the UPF may buffer the DLpackets for the one or more PDU Session(s) or may drop the DL packetsfor the one or more PDU sessions or may forwards the DL packets for theone or more PDU sessions to the SMF, based on buffering instructionprovided by the SMF. When the one or more PDU Sessions correspond to aLADN, the SMF may notify the UPF to discard downlink data for the one ormore PDU Sessions and/or to not provide further Data Notificationmessages. The SMF may invoke the Namf_Communication_N1N2MessageTransferservice operation (PDU Session ID, N2 SM Information (N2 ResourceRelease Request (PDU Session ID))) to release the NG-RAN resourcesassociated with the PDU Session. The AMF may send the N2 PDU SessionResource Release Command including N2 SM information (N2 ResourceRelease Request (PDU Session ID)) received from the SMF via N2 to theNG-RAN.

In an example, the Namf_Communication_N1N2MessageTransfer serviceoperation may comprise a group information, group identifier, and/or thelike as determined by the SMF. The NG-RAN may issue NG-RAN specificsignalling exchange (e.g. RRC Connection Reconfiguration) with the UEsto release the NG-RAN resources related to the one or more PDU Sessionsreceived from the AMF. When User Plane connections for the one or morePDU Sessions released, the AS layer in the UE may indicate it to the NASlayer. The NG-RAN may acknowledge the N2 PDU session resource releasecommand to the AMF including N2 SM Resource Release Ack (User LocationInformation, Secondary RAT Usage Data). The AMF may invoke theNsmf_PDUSession_UpdateSMContext service operation (N2 SMInformation(Secondary RAT Usage Data)) to acknowledge the Namf service.

In an example embodiment, a session management function (SMF) mayreceive from a user plane function (UPF), a data notification messagecomprising a multicast address. The SMF may determine based on themulticast address, a group information associated with a group of one ormore wireless devices. The SMF may send to an access and mobilitymanagement function (AMF), an activation request (e.g., N11 message,Namf message, and/or the like) comprising the group information. Theactivation request may indicate a request for activation of a user planeconnection or user plane resources for at least one wireless device ofthe group.

In an example, when the AMF receives an N11 message from the SMF thatcomprises the group information, multicast information, multicastaddress, and/or the like, the AMF may retrieve/obtain/determine one ormore wireless devices that are associated with the group based on one ormore elements of the N11 message. The AMF may determine to activate thewireless devices of the group. The AMF may determine that one or morewireless devices of the group are in idle mode e.g., CM-IDLE. The AMFmay send a paging message to the wireless devices in idle mode. The AMFmay send a paging message to activate user plane connection for thewireless devices. The wireless devices in response to receiving thepaging message may perform the UE triggered service request procedure.

The SMF may receive from the at least one wireless device, an activationrequest for user plane resources for a packet data unit (PDU) session ofthe at least one wireless device. The SMF may send to the UPF based onthe activation request, a session modification request for the PDUsession or N4 session of the at least one wireless device. The SMF maydetermine to activate an N4 session of the PDU session based on thegroup information. The data notification may indicate that the UPF hasreceived data packets for the group.

In an example, the SMF may send to the UPF, a packet detection rule(PDR) comprising the multicast address. The PDR may comprise aforwarding action rule (FAR). The SMF may configure the UPF to send datapackets to the group based on elements of the PDR and the FAR. In anexample, the data notification message further comprises a packetdetection rule identifier (PDR ID) associated with the group. In anexample, the data notification message may comprise an N4 session idassociated with a PDU session for the group, an identifier/address of aUPF associated with the group, and/or the like. The SMF may determinethe group information based on the identifier/address of a UPFassociated with the group, the N4 session ID, one or more elements ofthe data notification message, and/or the like. The SMF may determinethe group information based on the PDR ID.

In an example embodiment, a user plane function (UPF) may receive from awireless device, data packets for a group of wireless devices. The UPFmay determine that a destination address for the data packets is amulticast address. The UPF may determine a multicast information. TheUPF may determine to activate user plane connections/resources for thegroup of wireless devices. The UPF may send to a session managementfunction (SMF), a data notification message comprising the multicastaddress, multicast information, and/or the like. The UPF may receivefrom the SMF, a session modification message indicating a request foractivation of a user plane connection for at least one wireless deviceof the group. The UPF may send the data packets to the group and/or theat least one wireless device(s).

In an example, the sending the data packets may comprise sending thedata packets to the group. The group may be identified by the multicastaddress. The sending the data packets may comprise sending the datapackets to the at least one wireless device. The at least one wirelessdevice may be identified by a subscriber permanent identifier (SUPI).The at least one wireless device may be identified by a PDU sessionassociated with the at least one wireless device. The at least onewireless device may be identified by an N4 session associated with theat least one wireless device.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, a corenetwork device, a core network function, and/or the like, may compriseone or more processors and memory. The memory may store instructionsthat, when executed by the one or more processors, cause the device toperform a series of actions. Embodiments of example actions areillustrated in the accompanying figures and specification. Features fromvarious embodiments may be combined to create yet further embodiments.

FIG. 33 is an flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3310, a user plane function (UPF) mayreceive, from a session management function (SMF), a sessionconfiguration message. The session configuration message may comprise apacket detection rule (PDR) for a group communication session. The PDRmay comprise a multicast address mapped to a plurality of wirelessdevices associated with the group communication session. The PDR maycomprise a forwarding rule for packets associated with the multicastaddress. Data packets comprising the multicast address may be received.Based on the PDR, the data packets may be sent to the plurality ofwireless devices.

According to an embodiment, the plurality of wireless devices may beidentified by a PDU session associated with at least one wireless deviceof the plurality of wireless devices. According to an embodiment, theplurality of wireless devices may be identified by an N4 sessionassociated with at least one wireless device of the plurality ofwireless devices.

According to an embodiment, the UPF may send, to the SMF, a datanotification message for the data packets. The data notification messagemay comprise the multicast address. According to an embodiment, the datanotification message may comprise an N4 session identifier of a PDUsession associated with the group communication session. the datanotification message may comprise an identifier of the PDR.

According to an embodiment, the multicast address may comprise amulticast IP address. The multicast address may comprise a multicast MACaddress. According to an embodiment, the UPF may send, in response to aPDU session establishment request for the group communication session,multicast information to the plurality of wireless devices.

According to an embodiment, the forwarding rule may indicate whether tobuffer the data packets. According to an embodiment, the forwarding rulemay indicate an interface of the UPF for data packet forwarding.

In this specification, a and an and similar phrases are to beinterpreted as at least one and one or more. In this specification, theterm may is to be interpreted as may, for example. In other words, theterm may is indicative that the phrase following the term may is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments. If A and Bare sets and every element of A is also an element of B, A is called asubset of B. In this specification, only non-empty sets and subsets areconsidered. For example, possible subsets of B={cell1, cell2} are:{cell1}, {cell2}, and {cell1, cell2}.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and each of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example embodiment,when one or more messages comprise a plurality of parameters, it impliesthat a parameter in the plurality of parameters is in at least one ofthe one or more messages, but does not have to be in each of the one ormore messages.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, which may be behaviorally equivalent. For example,modules may be implemented as a software routine written in a computerlanguage configured to be executed by a hardware machine (such as C,C++, Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device.Finally, it needs to be emphasized that the above mentioned technologiesare often employed in combination to achieve the result of a functionalmodule.

Example embodiments of the invention may be implemented using variousphysical and/or virtual network elements, software defined networking,virtual network functions.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative embodiments. Thus, the presentembodiments should not be limited by any of the above describedexemplary embodiments. In particular, it should be noted that, forexample purposes, the above explanation has focused on the example(s)using 5G AN. However, one skilled in the art will recognize thatembodiments of the invention may also be implemented in a systemcomprising one or more legacy systems or LTE. The disclosed methods andsystems may be implemented in wireless or wireline systems. The featuresof various embodiments presented in this invention may be combined. Oneor many features (method or system) of one embodiment may be implementedin other embodiments. A limited number of example combinations are shownto indicate to one skilled in the art the possibility of features thatmay be combined in various embodiments to create enhanced transmissionand reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposes.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or optionally usedin some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language means for or step for be interpreted under 35 U.S.C.112. Claims that do not expressly include the phrase means for or stepfor are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a user planefunction (UPF) from a session management function (SMF), a sessionconfiguration message comprising a packet detection rule (PDR) for agroup communication session, wherein the PDR comprises: a multicastaddress mapped to a plurality of wireless devices associated with thegroup communication session; and a forwarding rule associated with themulticast address; receiving, by the UPF, multicast data for theplurality of wireless devices associated with the multicast address;sending, by the UPF to the SMF and based on the receiving the multicastdata, a data notification message indicating multicast data arrival;receiving, by the UPF from the SMF, a session modification requestindicating downlink tunnel information for the multicast data; andsending, by the UPF based on the downlink tunnel information, themulticast data to the plurality of wireless devices.
 2. The method ofclaim 1, wherein the plurality of wireless devices is identified by aPDU session associated with at least one wireless device of theplurality of wireless devices.
 3. The method of claim 1, wherein theplurality of wireless devices is identified by an N4 session associatedwith at least one wireless device of the plurality of wireless devices.4. The method of claim 1, wherein the data notification messagecomprises the multicast address.
 5. The method of claim 4, wherein thedata notification message further comprises an N4 session identifier ofa PDU session associated with the group communication session.
 6. Themethod of claim 4, wherein the data notification message furthercomprises an identifier of the PDR.
 7. The method of claim 1, whereinthe multicast address comprises: a multicast IP address; or a multicastMAC address.
 8. The method of claim 1, further comprising sending, bythe UPF to the plurality of wireless devices, multicast information inresponse to a PDU session establishment request for the groupcommunication session.
 9. The method of claim 1, wherein the forwardingrule indicates whether to buffer the multicast data.
 10. The method ofclaim 1, wherein the forwarding rule indicates an interface of the UPFfor data packet forwarding.
 11. A user plane function comprising: one ormore processors; memory storing instructions that, when executed by theone or more processors, cause the user plane function to: receive, froma session management function (SMF), a session configuration messagecomprising a packet detection rule (PDR) for a group communicationsession, wherein the PDR comprises: a multicast address mapped to aplurality of wireless devices associated with the group communicationsession; and a forwarding rule associated with the multicast address;receive multicast data for the plurality of wireless devices associatedwith the multicast address; and send, to the SMF and based on thereceiving the multicast data, a data notification indicating multicastdata arrival; receive, from the SMF, a session modification requestindicating downlink tunnel information for the multicast data; send,based on the downlink tunnel information, the multicast data to theplurality of wireless devices.
 12. The user plane function of claim 11,wherein the plurality of wireless devices is identified by a PDU sessionassociated with at least one wireless device of the plurality ofwireless devices.
 13. The user plane function of claim 11, wherein theplurality of wireless devices is identified by an N4 session associatedwith at least one wireless device of the plurality of wireless devices.14. The user plane function of claim 11, wherein the data notificationmessage comprises the multicast address.
 15. The user plane function ofclaim 14, wherein the data notification message further comprises: an N4session identifier of a PDU session associated with the groupcommunication session; and an identifier of the PDR.
 16. The user planefunction of claim 11, wherein the multicast address comprises: amulticast IP address; or a multicast MAC address.
 17. The user planefunction of claim 11, wherein the instructions, when executed by the oneor more processors, further cause the user plane function to send, tothe plurality of wireless devices, multicast information in response toa PDU session establishment request for the group communication session.18. The user plane function of claim 11, wherein the forwarding ruleindicates whether to buffer the multicast data.
 19. The user planefunction of claim 11, wherein the forwarding rule indicates an interfaceof the user plane function for data packet forwarding.
 20. A systemcomprising: a user plane function comprising: one or more firstprocessors; a first memory storing first instructions that, whenexecuted by the one or more first processors, cause the user planefunction to: receive, from a session management function (SMF), asession configuration message comprising a packet detection rule (PDR)for a group communication session, wherein the PDR comprises: amulticast address mapped to a plurality of wireless devices associatedwith the group communication session; and a forwarding rule associatedwith the multicast address; receive multicast data for the plurality ofwireless devices associated with the multicast address; send, to the SMFand based on the receiving the multicast data, a data notificationindicating multicast data arrival; receive, from the SMF, a sessionmodification request indicating downlink tunnel information for themulticast data; send, based on the downlink tunnel information, themulticast data to the plurality of wireless devices; and a sessionmanagement function comprising: one or more second processors; a secondmemory storing second instructions that, when executed by the one ormore second processors, cause the session management function to: send,to the user plane function, the session configuration message comprisingthe packet detection rule (PDR) for the group communication session,wherein the PDR comprises: the multicast address mapped to the pluralityof wireless devices associated with the group communication session; andthe forwarding rule for packets associated with the multicast address;receive, from the user plane function, the data notification; and send,to the user plane function, the session modification request.